Thanks Keith - I now have my code running as expected - calling the peek command to check if there are any jobs "ready" - if there are, the job is reserved - if there is no job, Pheanstalk throws an exception which I catch & stop processing. So that's the first steps into the beanstalkd app & thus far I really like the light weight appeal & ease to use.
Now to create a consumer daemon to process jobs non stop & at very large processing volumes. Will be good to see how performance holds up - are you able to give me any benchmarks as to what kind of loads beanstalkd can handle. Eg I thinking of around 5000 jobs a second with a small json payload. Curious as to if I will have to create multiple tubes to deal with load - or if this is a non issue. Any reading is appreciated. Thanks for all your help Keith - first thoughts are great & your responses have been accurate & timely. Kyle On Aug 20, 7:04 pm, Keith Rarick <[email protected]> wrote: > On Wed, Aug 19, 2009 at 6:16 PM, voomstudio.com<[email protected]> wrote: > > I have a consumer on a separate process with the same default > > 127.0.0.1:11300 config that "watches" this named queue of notification > > (ignoring default). The consumer tries to pull/consume jobs using the > > "peek-ready" option. So all jobs on this queue in a ready state should > > be available to be reserved. > > Try using the "reserve" or "reserve-with-timeout" command. Workers > don't normally need to use the peek commands. > > kr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
