cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3997) Make SerializingCache Memory Pluggable
Date Sat, 10 Aug 2013 04:42:48 GMT

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

Vladimir Rodionov commented on CASSANDRA-3997:
----------------------------------------------

A little bit late but better ever than never ...

"JEMalloc but the only issue with it is that (both TCMalloc and JEMalloc) are kind of single
threaded (at-least they crash in my test otherwise)."

JEmalloc must be configured with :
{code}
--disable-lazy-lock
    Disable code that wraps pthread_create() to detect when an application
    switches from single-threaded to multi-threaded mode, so that it can avoid
    mutex locking/unlocking operations while in single-threaded mode.  In
    practice, this feature usually has little impact on performance unless
    thread-specific caching is disabled.
{code}

jemalloc, by deafult wraps pthread API and tries to detect when when an application
    switches from single-threaded to multi-threaded mode. This trick does not work inside
JVM of course.


                
> Make SerializingCache Memory Pluggable
> --------------------------------------
>
>                 Key: CASSANDRA-3997
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3997
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>              Labels: cache
>             Fix For: 2.0 beta 1
>
>         Attachments: 0001-CASSANDRA-3997.patch, 0001-CASSANDRA-3997-v2.patch, 0001-CASSANDRA-3997-v3.patch,
0001-CASSANDRA-3997-v4.patch, jna.zip
>
>
> Serializing cache uses native malloc and free by making FM pluggable, users will have
a choice of gcc malloc, TCMalloc or JEMalloc as needed. 
> Initial tests shows less fragmentation in JEMalloc but the only issue with it is that
(both TCMalloc and JEMalloc) are kind of single threaded (at-least they crash in my test otherwise).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message