[zeromq-dev] ZMQ 2.1.0 and OpenPGM Memory Usage

Bob Beaty bobbeaty at comcast.net
Fri Dec 3 17:35:34 CET 2010

  Thanks so very much. I hadn't looked into all the options for the multicast and the ZMQ_RECOVERY_IVL is indeed the key.
  Question: It's now in seconds. Is there any way to make it "tenths of a second"? I'd like to make it about 0.5sec as my application is very much "if you're here, good... if not, hit the cache".


On Dec 3, 2010, at 10:02 AM, Martin Sustrik wrote:

> On 12/03/2010 04:56 PM, Bob Beaty wrote:
>>   This is where it gets interesting.
>>   Below is the table of ZMQ_RATE size versus the "terminal memory
>> footprint" of the application.
>> 	bps       ZMQ_RATE     Size (after 2000 ... terminal)
>> 	10Mbps      10000         7MB ... 18MB
>> 	50Mbps      50000         7MB ... 73MB
>> 	200Mbps    200000         7MB ... 280MB
>>   At this point I realized that it's not a leak - it's something like a
>> buffer growth related to the anticipated need based on the maximum speed.
> Isn't it just the TX buffer? The size of PGM's TX buffer can be be computed as ZMQ_RATE * ZMQ_RECOVERY_IVL. The messages are held in memory even after they are sent to allow retransmission (repair) for the period of ZMQ_RECOVERY_IVL seconds.
> Martin

        Bob (drbob at TheManFromSPUD.com)
    The Man from S.P.U.D.
    We will write no code before it's designed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101203/63b0b8e1/attachment.htm>

More information about the zeromq-dev mailing list