[jira] [Commented] (ARTEMIS-3335) Improve Artemis Thread affinity

["Francesco Nigro (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17362311#comment-17362311 ] 

Francesco Nigro commented on ARTEMIS-3335:
------------------------------------------

It worth to check https://github.com/hazelcast/hazelcast/pull/17435 becuse using OpenHFT doesn't seem an option for some users.

> 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
>            Priority: Major
>
> 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 exposing the right hooks to perform programmatically and/or automatically such tuning 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 OpenHFT one in case ad-hoc ones cannot be used (see https://github.com/hazelcast/hazelcast/commit/a7e7defde2086b20a3af93e6d59ff4fadfd06ae4)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)