[
https://issues.apache.org/jira/browse/CASSANDRA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244151#comment-13244151
]
Pavel Yaskevich edited comment on CASSANDRA-3997 at 4/2/12 12:33 PM:
---------------------------------------------------------------------
Howard allocator uses even more memory (~300 MB more) than standard allocator
but jemalloc buys as ~2.5 GB which is pretty good. The last thing here would be
to investigate what causes free() segfaults with jemalloc so different memory
allocators could be used without any structural changes to the code...
Would be helpful if you could describe here the situation when that segfault
happens.
was (Author: xedin):
Howard allocator uses even more memory (~300 MB more) than standard
allocator but jemalloc buys as ~2.5 GB which is pretty good. The last thing
here would be to investigate what causes free() segfaults with jemalloc so
different memory allocators could be used without any structural changes to the
code...
> 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
