I'm sure beanstalkd can handle the traffic (I'm processing more than that already from a few other servers). My question was more related to the fact that these will all be delayed jobs and I don't know how beanstalkd handles managing when they become ready. I was concerned it would add a lot of overhead.
On Thu, Jan 20, 2011 at 1:05 AM, Dustin <[email protected]> wrote: > > On Jan 19, 8:42 pm, Chad Kouse <[email protected]> wrote: >> 187,500 jobs sitting on average right? 4,500,000 / 24 > > Yeah, I wasn't paying much attention and ended up doing some weird > calculation for something else. I can't even remember what now. :/ > > You'd be adding about (5M / 86400) 60 jobs per seconds and grabbing > about the same after getting up to your estimated peak. That's pretty > easy to test, but I'm certain I've done more than that. :) > > -- > 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. > > -- 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.
