I changed the "sleep(1)" in durapub2.c to "usleep(10)", make the loop run infinitely, start durapub2 and durasub, ctrl-c durasub, and I am seeing that the allocated memory of durapub2 keep raising just like never hitting a limit at all! However, I set the HWM to only 5.
On Wed, Jul 27, 2011 at 4:59 PM, Ian Barber <[email protected]> wrote: > On Wed, Jul 27, 2011 at 5:26 AM, Tonis Xie <[email protected]> wrote: > >> >> >Also note that you'll almost certainly push more than HWM messages, as >> some will sit in TCP buffers. Being that the messages are >only 20 bytes, >> that could be quite a few. >> >> If this could happen, how can we get the same effect as the durapub2 >> example that is described in zguide? >> >> -tonis >> > > HWM is not designed to be a precise limit - it's designed to stop the stack > from running out of memory. If you are seeing the publisher overflowing > available memory, or never hitting a limit at all, then I would be > concerned, but in general HWM is not for precise flow control or > backpressure. > > Ian > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
