Just wanted to say thanks for beanstalkd. The app I have at work tried a couple different message queues in the past (a database backed one being used in production; a redis backed one; and just finished testing a few other ones as candidates to replace it). For this app, beanstalkd's working much better than the others for me.
Perhaps my messages aren't typical for these other queues -- a few times a week millions of short (few byte) messages get queued in rather quick (few minute long) bursts; while a couple dozen workers process them continually. With the other queues I tried -- some of them didn't like seeing 4 million messages suddenly inserted in the queue -- and with others it seems half the computers' time was spent juggling messages in the queues with lots of fork()s or sync()s instead of doing real work. With beanstalkd the queue overhead's down in the noise and throughput of the system just about doubled. -- 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.
