[Backgroundrb-devel] BackgrounDRb version 1.0RC1 available now
gethemant at gmail.com
Wed Nov 14 09:57:42 EST 2007
On Nov 14, 2007 8:13 PM, hemant <gethemant at gmail.com> wrote:
> On Nov 14, 2007 7:57 PM, Brandon Keepers <brandon at opensoul.org> wrote:
> > On Nov 14, 2007, at 8:55 AM, hemant wrote:
> > > On Nov 14, 2007 6:50 PM, Wood, Peter <p.wood at lancaster.ac.uk> wrote:
> > >> Heya all,
> > >>
> > >> A coworker and I have checked out the new version of BackgrounDRb in
> > >> order to build one of our latest projects, so far we've just tried to
> > >> replicate some of the functionality we had when testing the old trunk
> > >> version.
> > >>
> > >> I may be missing something obvious, but from the code it doesn't
> > >> appear
> > >> that you can set off multiple copies of the same worker like you
> > >> could
> > >> in the old trunk version. We intend to use BackgrounDRb to set off
> > >> snmp
> > >> scans of various devices on our network, some of which take some
> > >> time to
> > >> complete. It is likely that this will happen more than once at any
> > >> particular moment in time.
> > >>
> > >> At the moment, using the sample code we've moved the reply to the
> > >> MiddleMan to before the work, therefore actually letting the calling
> > >> application carry on (which is what we need). However a second call
> > >> to
> > >> the same worker obviously hangs until the first call has completed.
> > >>
> > >> I think what I'm essentially saying is that we want multiple
> > >> instances
> > >> of the same worker which can be identified by a key (as it was in the
> > >> trunk). Is this possible with the new version of BackgrounDRb, or
> > >> is it
> > >> on the map?
> > >>
> > >
> > > With new version you can't have two instances of a worker active at
> > > the same time. Although, I do think of having that facility soon, but
> > > for the time being you will have to put up with writing copies of
> > > workers. BTW, how many copies do you need and how much time, does
> > > it take to complete scan of devices on network?
> > This is a show stopper for me. The only thing I've ever used
> > BackgrounDRb for it firing off workers at will to do various
> > processing tasks, such as transferring large files or transcoding
> > video. If I have a quad core CPU, I want 4 instances of the same
> > worker running in order to take full advantage of the CPU.
> Ok, then folks, I will be implementing it. Will be available soonish.
Ok, on second thoughts, I was curious about the fact, that can't you
have 4 different workers running at the same time?
Why you need copies of same workers? I know, you don't have to write
additional worker code, if you use the same worker, but
apart from that what?
You can very well have 4 four workers like:
You can very well do, whatever you want inside them. Another question
is, how do you schedule workers ( which are instance of same class?).
use cron based scheduling or Scheduling using MiddleMan or what?
I am not trying to dodge, but just want to understand full use case.
Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
More information about the Backgroundrb-devel