[
https://issues.apache.org/jira/browse/ARTEMIS-3303?focusedWorklogId=598356&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-598356
]
ASF GitHub Bot logged work on ARTEMIS-3303:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/21 00:01
Start Date: 18/May/21 00:01
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, as you know we've been hit a few
times by such sort of changes, which impacted users/we reverted in later
releases.
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, high client use cases, low
client use cases.
Id much more favour ability to document better tuning, and tools that enable
to auto tune / give defaults to the broker better, for different known certain
use cases / setups, than can be setup during broker creation. Akin to the tool
we have for journal, where it perf tests the disk and then sets a suitable
values based off the observed kits.
--
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: 598356)
Time Spent: 2h 20m (was: 2h 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: 2h 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)
