activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-905) JCtools ConcurrentMap replacement
Date Wed, 01 Feb 2017 11:12:52 GMT

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

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

Github user franz1981 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/945
  
    @ig-michaelpearce No problem, I'll be more than happy to check it out and try to understand
what could be happened; my personal email is on the GitHub profile


> 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)

Mime
View raw message