On 05/01/2014 03:09 PM, Rafael Schloming wrote:
On Thu, May 1, 2014 at 9:36 AM, Michael Goulish <[email protected]> wrote:
Since I reported earlier that 1 messenger-based sender grew to
3.4 GB after sending to 30,000 unique addrs, it seems reasonable
that 1000 messenger-based receivers, attempting to receive from a total
of 1,000,000 addrs, would have attempted to grow to a total of more
than 100 GB. Which would account very nicely for the behavior I saw.
( The box had 45 GB mem. )
It would be worth actually confirming the growth of memory as you start
your receivers. The memory usage on the sender side isn't necessarily
the same as on the receiver side (depends of course what the memory is
being used for).
The receive side is a bit different, and using qpid-messaging will not
necessarily help you scale up. Fundamentally in order to receive messages
from N different addresses you need to create N subscriptions. That's going
to be just as expensive regardless of which API you use to do it.
On the client side, an extra subscription shouldn't require a great deal
of extra memory though, at least I wouldn't expect it to.
The one
option you might have with qpid-messaging is that you can close your
receivers explicitly, whereas messenger doesn't have a way to cancel
subscriptions. This isn't really a matter of intent though, it's just a
missing feature.
I don't believe that would help in this test, since all the receivers
are active before the sender starts.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
