[zeromq-dev] trying to understand zeromq high water mark behaviour

Goswin von Brederlow goswin-v-b at web.de
Thu Jan 30 16:48:48 CET 2014

On Mon, Jan 27, 2014 at 09:06:42PM +0000, Shaobo Hou wrote:
> Thanks Pieter,
> I had another look at the output, and it does look like maybe the TCP
> buffer is involved somehow, the messages received by the slow worker were
> all from the beginning of the test sequence, so presumably they were sent
> out before the sockets started blocking due to HWM.
> Shaobo

One thing that was mentioned was that one should be carefull about the
timing. When you send out jobs and then one worker connects then it
will grab all messages it can get. Then when the second worker
connects there might be no work left.

So you probably want to start all the worker and have them send an ACK
once they are connected and only then start queuing up jobs or so.


More information about the zeromq-dev mailing list