[
https://issues.apache.org/jira/browse/CAMEL-14247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825626#comment-17825626
]
Yih Tsern commented on CAMEL-14247:
-----------------------------------
{*}Note for fellow users{*}: While the property name is unchanged,
*NettyComponent.maximumPoolSize* has been changed to mean "minimum pool size"
instead - to illustrate:
h3. Before CAMEL-14247
||CPU core||maximumPoolSize=16 (default)||
|1|16 concurrent Exchanges|
|6|16 concurrent Exchanges|
|12|16 concurrent Exchanges|
|16|16 concurrent Exchanges|
|20|16 concurrent Exchanges|
h3. After CAMEL-14247
||CPU core||maximumPoolSize=0 (default)||maximumPoolSize=16||
|1|3 concurrent Exchanges|16 concurrent Exchanges|
|6|13 concurrent Exchanges|16 concurrent Exchanges|
|12|25 concurrent Exchanges|25 concurrent Exchanges|
|16|32 concurrent Exchanges|32 concurrent Exchanges|
|20|41 concurrent Exchanges|41 concurrent Exchanges|
> camel-netty - Turn off component level shared thread pool and use nettys
> workers directly
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-14247
> URL: https://issues.apache.org/jira/browse/CAMEL-14247
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty
> Affects Versions: 3.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.1.0
>
>
> There is a shared worker pool on the component level that has 16 threads out
> of the box. You can turn this off as said before and it uses nettys worker
> threads directly. So that pool would be shared if you have more netty
> consumers eg maybe 2 or more routes that start from netty.
> Today I am not sure if it was a good idea to have a 16 thread pool by default
> that is shared among all netty consumers in the same Camel app.It should
> possible have been turned off, and just use the netty worker threads directly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
