On Thu, Dec 6, 2012 at 11:52 AM, Chad Kouse <[email protected]> wrote: > Just curious, why is it better to put all jobs through a single tube?
In queueing theory terms, a single queue with N servers is more efficient than N queues with one server each. In beanstalkd terms a "queue" is a tube and a "server" is a worker. Now, since a beanstalkd worker can listen on multiple tubes, having two tubes is just as good as one tube if all workers are listening on both tubes. The thing to avoid (unless of course there's a good reason for it) is some workers on just one tube and other workers on a different tube. I have yet to find a good explanation online to convey intuition for why this is so. It would make a good blog post. -- 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.
