You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Francesco Nigro (Jira)" <ji...@apache.org> on 2021/06/07 10:45:00 UTC
[jira] [Created] (ARTEMIS-3335) Improve Artemis Thread affinity
Francesco Nigro created ARTEMIS-3335:
----------------------------------------
Summary: Improve Artemis Thread affinity
Key: ARTEMIS-3335
URL: https://issues.apache.org/jira/browse/ARTEMIS-3335
Project: ActiveMQ Artemis
Issue Type: New Feature
Components: Broker, Configuration
Reporter: Francesco Nigro
https://issues.apache.org/jira/browse/ARTEMIS-3303, https://issues.apache.org/jira/browse/ARTEMIS-3289 and https://issues.apache.org/jira/browse/ARTEMIS-3045 shown how much it worth to improve the mechanical sympathy of broker, regardless specific hardware.
A well tuned broker can easily improve performance and helping users to expose the right hook to perform programmatically and/or automatically such tunings is a nice addition and traction for high-performance scenarios.
Thread affinity plays a big role on this and there are already Apache libraries that could help setting it for specific thread pools in the broker (global thread pool, I/O thread pool, netty acceptor thread pools, netty connector thread pools, timed buffer thread, ASYNCIO background thread etc etc) eg https://github.com/OpenHFT/Java-Thread-Affinity
There are other project that employ an ad-hoc affinity strategy eg Hazelcast, failback to OpenFT one in case ad-hoc cannot be used (see https://github.com/hazelcast/hazelcast/commit/a7e7defde2086b20a3af93e6d59ff4fadfd06ae4)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)