[
https://issues.apache.org/jira/browse/ARTEMIS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135153#comment-16135153
]
ASF GitHub Bot commented on ARTEMIS-1356:
-----------------------------------------
GitHub user franz1981 opened a pull request:
https://github.com/apache/activemq-artemis/pull/1477
ARTEMIS-1356 Avoid allocations and atomic operations to recognize handler's
thread
Uses a cached marker instance to recognize an handler's thread, avoiding
allocations and atomic operations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/franz1981/activemq-artemis gc_free_recursion
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1477.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 #1477
----
----
> Avoid allocations and atomic operations to recognize handler's thread
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-1356
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1356
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
>
> The current way to recognize the handler's thread is using heavyweight
> operations (allocations + atomic set/get) that limit some compiler
> optimizations on the (core) packet handling path.
> The same logic can be achieved using only a ThreadLocal map and a cached
> marker instance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
