cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3997) Make SerializingCache Memory Pluggable
Date Tue, 06 Mar 2012 19:23:56 GMT


Vijay commented on CASSANDRA-3997:

Hi Jonathan, The good thing is that it saves us from the Memory Fragmentation which we have
seen with the native malloc's after it runs for a prolonge period of time. If the user wants
to use a different implementation they can use it. JEMAlloc hasn't segfault in any of my tests
I think it is better to use we still need to do more tests per sure.

>>> Does this preserve the ability to use Unsafe instead of a JNA-backed malloc?
No, the ticket just makes it pluggable so any other implementation is possible. We dont need
to build the *.so/dll's for every environment we come across and the unsafe can be default
> Make SerializingCache Memory Pluggable
> --------------------------------------
>                 Key: CASSANDRA-3997
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>              Labels: cache
>             Fix For: 1.2
>         Attachments:
> 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:!default.jspa
For more information on JIRA, see:


View raw message