You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/09 22:49:37 UTC

[jira] [Commented] (ARTEMIS-905) JCtools ConcurrentMap replacement

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

ASF GitHub Bot commented on ARTEMIS-905:
----------------------------------------

Github user clebertsuconic commented on the issue:

    https://github.com/apache/activemq-artemis/pull/945
  
    @franz1981 can you either rework this or close it?


> JCtools ConcurrentMap replacement
> ---------------------------------
>
>                 Key: ARTEMIS-905
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-905
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Francesco Nigro
>            Priority: Minor
>
> The OSS project JCTools (already used in Netty core) provides primitive (long) and normal implementations of ConcurrentMap with better scalability, lower memory footprint (garbage collector wise too) and equals to better performances than the vanilla's ConcurrentHashMap.
> It worth to replace every ConcurrentHashMap usage with the JCtools version.
> [Here|http://www.azulsystems.com/blog/cliff/2007-03-26-non-blocking-hashtable] there is an old but valid overview of the map and on JCtools are provided [JMH benchmarks|https://github.com/JCTools/JCTools/blob/master/jctools-benchmarks/src/main/java/org/jctools/maps/nhbm_test/jmh/ConcurrentMapThroughput.java] to evaluate the performance of the implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)