Hi, Barber I have tried your suggestion(commenting out the SWAP), and sleep(1) and set HWM to 5. But it was still the same(HWM no effect):
xzc@debian1:~/zmq/zguide/examples/C$ ./durasub Update 0 Update 1 Update 2 Update 3 Update 4 ^C (...wait about 10 seconds) xzc@debian1:~/zmq/zguide/examples/C$ ./durasub Update 5 Update 6 Update 7 Update 8 Update 9 Update 10(supposed to be dropped) Update 11(supposed to be dropped) Update 12(supposed to be dropped) Update 13(supposed to be dropped) Update 14(supposed to be dropped) Update 15(supposed to be dropped) Update 16 Update 17 Update 18 Update 19 Update 20 Update 21 Update 22 >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 On Tue, Jul 26, 2011 at 10:58 PM, Ian Barber <[email protected]> wrote: > > > On Tue, Jul 26, 2011 at 3:50 PM, Tonis Xie <[email protected]> wrote: > >> >> Based on the above, I guess the high water mark had no effect at all! >> >> > Note that durapub2 does have SWAP defined. Try commenting that out, and > see if the behavior is more as you expected. Doesn't sound quite like the > right behavior for SWAP either, but that may be a separate issue. > > 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. > > 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
