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/01/02 14:54:58 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=15792992#comment-15792992 ] 

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

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/945

    ARTEMIS-905 JCtools ConcurrentMap replacement

    It's a total replacement of ConcurrentHasMap and ConcurrentHashSet usage with faster and lower memory footprint versions of jctools; a high performance concurrent collections library.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/activemq-artemis chm_replacement

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/945.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 #945
    
----
commit fe40c1ba2153b110be329175142e494643602093
Author: Francesco Nigro <ni...@gmail.com>
Date:   2017-01-02T14:50:53Z

    ARTEMIS-905 JCtools ConcurrentMap replacement

----


> JCtools ConcurrentMap replacement
> ---------------------------------
>
>                 Key: ARTEMIS-905
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-905
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Francesco Nigro
>
> 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.4#6332)