[rabbitmq-discuss] What is a good tradeoff for number of connections and channels/connection for a client ?

Arun Suresh arun.suresh at gmail.com
Thu Jul 22 18:21:25 BST 2010

oh okay.. thanx for the response guys...

Like uve guessed, we do have need for multiple channels. Basically, we have
a large number of consumers each listening for messages on their own
specific queuus. So for each consumer, we have to create a channel.. and
yes.. like uve guessed, we do enforce certain specific qos settings on there

So is it safe for me to assume, that like Alex mentioned, there should NOT
be any issue if I create ALL the channels on the same connection ?


On Thu, Jul 22, 2010 at 10:34 PM, Matthew Sackman <matthew at rabbitmq.com>wrote:

> On Thu, Jul 22, 2010 at 05:59:53PM +0100, Alexandru Scvortov wrote:
> > Otherwise, there shouldn't be any reason to have multiple channels.
> Well, channels are stateful so for example you either have a
> transactional channel or a non transactional channel. That's a reason to
> have multiple channels. Also if you want different qos settings in
> different channels then that's a reason, also the meaning of
> ack{multiple=true} is obviously scoped by the non-acked msgs received in
> each channel. Thus there are some reasons to have multiple channels. But
> generally creating a pool of them or connections is, as Alex says, a bad
> idea.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100722/aa1ffdb1/attachment.htm>

More information about the rabbitmq-discuss mailing list