You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2012/07/31 19:16:35 UTC

[jira] [Updated] (APLO-163) Consider auto-tuning the per-connection buffers (receive_buffer_size and send_buffer_size)

     [ https://issues.apache.org/jira/browse/APLO-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-163:
-------------------------------

    Fix Version/s:     (was: 1.4)
                   1.5
    
> Consider auto-tuning the per-connection buffers (receive_buffer_size and send_buffer_size)
> ------------------------------------------------------------------------------------------
>
>                 Key: APLO-163
>                 URL: https://issues.apache.org/jira/browse/APLO-163
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>            Reporter: Lionel Cons
>             Fix For: 1.5
>
>
> As seen in APLO-160, the size of the per-connection buffers can greatly impact the memory usage.
> 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 buffers).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira