[Backgroundrb-devel] Best way to organize workers

hemant gethemant at gmail.com
Mon Feb 4 14:25:40 EST 2008

On Feb 5, 2008 12:37 AM, Scott Ward <scott at shefield.com> wrote:
> Hello,
> I have a few tasks that run every few minutes.  They definitely need their
> own worker.
> However, other tasks run once per day or even once per week.  Right now I am
> creating a new worker for each of these tasks, but I wonder if that's
> unnecessary for tasks that I know will never execute at the same time.  They
> don't need to run concurrently.
> Basically, I am wondering if I should combine a bunch of these periodic,
> non-overlapping tasks into one worker called "general_maintenance_worker" or
> something like that.  For each task, I could create a different method and
> schedule them as needed in backgroundrb.yml.
> That should work, but is it "right"?  What's the "best practice" is in this
> situation?

Yup, if your tasks are non-overlapping then you can put them in the
same worker and through backgroundrb.yml
you can configure them to run at different intervals.

Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
own coals.


More information about the Backgroundrb-devel mailing list