[
https://issues.apache.org/jira/browse/ARTEMIS-3303?focusedWorklogId=598348&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-598348
]
ASF GitHub Bot logged work on ARTEMIS-3303:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/May/21 23:50
Start Date: 17/May/21 23:50
Worklog Time Spent: 10m
Work Description: michaelpearce-gain edited a comment on pull request
#3584:
URL: https://github.com/apache/activemq-artemis/pull/3584#issuecomment-842715440
Im always cautious about such changes, after all one default for one org, is
different to another's use case in another org. And those using defaults and
tested with those, will get sudden un-expected shocks should they change. e.g.
you normally trade throughput for latency, or x for y ... its always a
trade.... Unless there stats showing performance improvement across the board
for all the main different types of setups our users have. e.g. high throughput
users, low throughput users, low latency users, mqtt users, amqp users, core
users, bare metal users vs virtualised users, users who care about the 50th
percentile, users who care about the fat tails 99.99ths percentiles and max.
--
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: 598348)
Time Spent: 1h 40m (was: 1.5h)
> 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: 1h 40m
> 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)
