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

Matthew Sackman matthew at rabbitmq.com
Thu Jul 22 18:04:50 BST 2010

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


More information about the rabbitmq-discuss mailing list