[
https://issues.apache.org/jira/browse/CASSANDRA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237722#comment-13237722
]
Vijay commented on CASSANDRA-3997:
----------------------------------
Have an update:
Jason Evan's says: "LD_PRELOAD'ing jemalloc should be okay as long as the JVM
doesn't statically link a different malloc implementation. I expect that if it
isn't safe, you'll experience crashes quite early on, so give it a try and see
what happens."
I have also conformed the unsafe isn't statically linked to native Malloc by
adding a printf in the malloc c code which basically count's the number of
times it is called. Looks like PRELOAD is a better option. I am running a long
running test and will close this ticket once it is successful. Thanks!
> 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: 1.2
>
> Attachments: 0001-CASSANDRA-3997.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
