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 2018/02/28 07:09:00 UTC
[jira] [Closed] (ARTEMIS-1702) ConcurrentLongHashMap and
ConcurrentLongHashSet should avoid volatile set cost on put/remove
[ https://issues.apache.org/jira/browse/ARTEMIS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Nigro closed ARTEMIS-1702.
------------------------------------
Resolution: Fixed
> ConcurrentLongHashMap and ConcurrentLongHashSet should avoid volatile set cost on put/remove
> --------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1702
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1702
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.5.0
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Minor
> Fix For: 2.5.0
>
>
> ConcurrentLongHashSet/HashMap are making use of unecessary volatile store of size/capacity for modifier methods.
> The current JVM implementation of volatile store for multicore x86 is making use of a StoreLoad barrier for this operation: the most expensive one.
> These volatile stores could be replaced by plain stores/lazySet ones with no effects on the correctness of those methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)