[
https://issues.apache.org/jira/browse/ARTEMIS-3303?focusedWorklogId=600691&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-600691
]
ASF GitHub Bot logged work on ARTEMIS-3303:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/21 23:00
Start Date: 21/May/21 23:00
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on pull request #3584:
URL: https://github.com/apache/activemq-artemis/pull/3584#issuecomment-846301161
can't you change ./artemis create to take the correct counting, and apply
the new defaults on new created servers?
users moving older tested configurations wouldn't be affected by anything...
new brokers would then use the "new defaults" and it would be up to the user to
decide on what to do...
we can always log.info (" We recommend new values now.. please change your
settings");
--
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: 600691)
Time Spent: 3h 50m (was: 3h 40m)
> 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 50m
> 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)
