GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/1263
ARTEMIS-1156: FIX: Long Autoboxing occurring on Hot Path
Building on ARTEMIS-905 JCtools ConcurrentMap replacement first proposed
but currently parked by @franz1981, replace the collections with primitive key
concurrent collections to avoid auto boxing.
The goal of this is to reduce/remove autoboxing on the hot path.
We are just adding jctools to the broker (should not be in client
dependencies)
Like wise targeting specific use case with specific implementation rather
than a blanket replace all.
We have to create our own primitive long concurrent hash set, based on
jctools as jctools currently don't have one.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michaelandrepearce/activemq-artemis
ARTEMIS-1156
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1263.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1263
----
commit 7f8b0077a6717f023387c1bc42db23229c47a9c6
Author: Michael Andre Pearce <[email protected]>
Date: 2017-05-10T07:13:24Z
ARTEMIS-1156: FIX: Long Autoboxing occurring on Hot Path
Building on ARTEMIS-905 JCtools ConcurrentMap replacement first proposed
but currently parked by @franz1981, replace the collections with primitive key
concurrent collections to avoid auto boxing.
The goal of this is to reduce/remove autoboxing on the hot path.
We are just adding jctools to the broker (should not be in client
dependencies)
Like wise targeting specific use case with specific implementation rather
than a blanket replace all.
We have to create our own primitive long concurrent hash set, based on
jctools as jctools currently don't have one.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
