[zeromq-dev] multiple bind with one socket

Martin Sustrik sustrik at 250bpm.com
Fri Oct 1 17:01:14 CEST 2010

Hi Kelly,

>> The rationale here is that two distinct message flows should not share
>> single TCP connection as it would result in so called head-of-line
>> blocking, i.e. large message being transferred in one message flow could
>> block the other flow for extended period of time.
> 	I understand this reasoning fine.  But, for some of my purposes, I'm
> more concerned about multiple sockets and the bandwidth required for the tcp
> flow control as I scale up the number of connections.  By design, 0mq seems
> to encourage a considerable number of sockets, which is fine, but if you are
> balancing bandwidth versus latency etc, sometimes merging the sockets can be
> a large win.  This is especially true as wan connections are considered.

Can you be more specific about the scenario?

How come multiple sockets use more bandwidth than a single one?


More information about the zeromq-dev mailing list