activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (Commented) (JIRA)" <>
Subject [jira] [Commented] (APLO-163) Consider auto-tuning the per-connection buffers (receive_buffer_size and send_buffer_size)
Date Tue, 03 Apr 2012 08:20:25 GMT


Lionel Cons commented on APLO-163:

There are two other similar parameters that could be tuned: tail_buffer (per queue) and buffer_size
(per STOMP connection).
> Consider auto-tuning the per-connection buffers (receive_buffer_size and send_buffer_size)
> ------------------------------------------------------------------------------------------
>                 Key: APLO-163
>                 URL:
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>            Reporter: Lionel Cons
>             Fix For: 1.3
> As seen in APLO-160, the size of the per-connection buffers can greatly impact the memory
> Since it can be difficult to predict how many concurrent connections will have to be
handled by the broker, it would be good if the broker could auto-tune the buffer sizes.
> The broker should be able to get JVM memory information and decide how much space should
be devoted to connection buffers (as opposed to other memory usages). Then, based on the number
of existing connections and the total buffer space they occupy, the broker could tune the
per-connection buffer sizes of the new connections (at least, it could also adjust the existing

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message