[rabbitmq-discuss] Queues versus Bindings

danb danb at aeriandi.com
Thu Apr 18 16:53:22 BST 2013

For my scenario, what's better: a queue with 6000 bindings, or 6000 queues
each with one binding?

My Scenario:

In my application I'd expect perhaps 1 to 20 messages per "binding" over
about 3 minutes. So if I take the many queues approach the queues will be
mostly idle, and I would destroy the queue after around 3 minutes so they
would be relatively short lived. I only have one process listening to the
messages using one connection with multiple channels.

Note: 6000, over 3 minutes means I'll be creating and deleting 33 queues per
second. Or alternatively adding or removing 33 bindings per second.

In the thread
Emile mentions that Rabbit can declare an "enormous number of idle queues
without difficulty". But I remember reading that Rabbit uses one Thread per
Queue, so I'm wondering what an enormous number is? 

Many Thanks!



View this message in context: http://rabbitmq.1065348.n5.nabble.com/Queues-versus-Bindings-tp26082.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list