You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/01/08 00:56:39 UTC
[jira] [Updated] (PROTON-568) messenger client slows and grows with
large address space
[ https://issues.apache.org/jira/browse/PROTON-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-568:
-------------------------------
Labels: messenger (was: )
> messenger client slows and grows with large address space
> ---------------------------------------------------------
>
> Key: PROTON-568
> URL: https://issues.apache.org/jira/browse/PROTON-568
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: michael goulish
> Labels: messenger
>
> A messenger-based sending client grows from little memory to over 3 GB, and slows down by at least 10x, when transmitting 1 message each to many addresses.
> here is the setup:
> 1. a single messenger-based sender.
> 2. a single dispatch router
> 3. 5000 messenger-based receivers, each listening to 10 unique addresses. i.e. 50,000 unique addresses total.
> 4. the sender sends a single to each unique address.
> 5. the first 10 messages go to addr1 ... addr10 -- all of which belong to the first receiver.
> 6. when each receiver gets all 10 of its messages, it shuts down.
> 7. each message is 1-to-1, and fire-and-forget.
> 8. This means that the sender only sends 1 message to each address and then moves on, never to return.
> Result
> -----------------------------------
> The sending application started out doing something like 100-200 messages per second. Its memory footprint was small.
> By the time I reach 13,000 messages sent, output has fallen to about 25 messages per second, and memory (RSS) has risen to about 1.7 GB.
> It keeps getting larger and slower until the user rebels.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)