[
https://issues.apache.org/jira/browse/QPID-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936633#comment-14936633
]
Keith Wall commented on QPID-6741:
----------------------------------
This change does not seem to be working as intended. On a machine with a large
number of cores, on first use, it scales the number of the threads in the pool
to the maximum size. This seems to have even if the pool already contains
sufficient threads to service the request.
> ThreadPoolExecutors used for virtual host IO / port IO do not scale above
> minimum pool size
> -------------------------------------------------------------------------------------------
>
> Key: QPID-6741
> URL: https://issues.apache.org/jira/browse/QPID-6741
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Keith Wall
> Fix For: qpid-java-6.0
>
>
> NetworkConnectionScheduler uses a {{java.util.concurrent.ThreadPoolExecutor}}
> to service AMQP IO. The intention is that the executor will dynamically
> scale the number of threads in the pool as load increases until a maximum is
> reached and then at that point requests will be queue. However, TPE, out of
> the box, does not offer such behaviour. When used with a unbounded queue,
> TPE will *never* increase the threads beyond the core size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
