[
https://issues.apache.org/jira/browse/ARTEMIS-3303?focusedWorklogId=598510&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-598510
]
ASF GitHub Bot logged work on ARTEMIS-3303:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/21 09:45
Start Date: 18/May/21 09:45
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #3584:
URL: https://github.com/apache/activemq-artemis/pull/3584#issuecomment-843023532
In short, I see no harm into reducing a bit the requirements for both thread
pools, at least getting:
- netty to use N cores
- global thread pool to use N cores
Leaving the OS to handle, via context switches, the fairness of task
executions among both.
I've decided (in this PR) to use half the core for both because of GC and
background OS threads that can handle disk/networking tasks too.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 598510)
Time Spent: 3h 20m (was: 3h 10m)
> Default thread pool size is too generous
> ----------------------------------------
>
> Key: ARTEMIS-3303
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3303
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> By tweaking thread pool size from default it's possible to easily gain twice
> the troughput: both Netty (acceptor) and global thread pool default sizing
> seems too generous according the available cores of a machine:
> * 3 x cores for the former
> * [0, 30] for the latter (!!!)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
