[
https://issues.apache.org/jira/browse/CASSANDRA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125188#comment-14125188
]
Jay Patel commented on CASSANDRA-7883:
--------------------------------------
Hi Benedict,
"memory_allocator" is the one used for off-heap caches and other metadata. I'm
re-using the same property.
>> From cassandra.yaml
# The off-heap memory allocator. Affects storage engine metadata as
# well as caches. Experiments show that JEMAlloc saves some memory
# than the native GCC allocator (i.e., JEMalloc is more
# fragmentation-resistant).
#
# Supported values are: NativeAllocator, JEMallocAllocator
#
# If you intend to use JEMallocAllocator you have to install JEMalloc as
library and
# modify cassandra-env.sh as directed in the file.
#
# Defaults to NativeAllocator
memory_allocator: JEMallocAllocator
> Allow plugging JEMalloc for off-heap memtables
> ----------------------------------------------
>
> Key: CASSANDRA-7883
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7883
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jay Patel
> Assignee: Jay Patel
> Labels: patch
> Fix For: 2.1.1
>
> Attachments: trunk-7883.txt
>
>
> Off-heap memtables (memtable_allocation_type:offheap_objects) introduced by
> CASSANDRA-6694 uses native GCC allocator. Provide an option to use JEMalloc
> allocator (http://www.canonware.com/jemalloc/) which is good to reduce
> fragmentation.
> CASSANDRA-3997 adds below option for off-heap caches and metadata. But it's
> not in effect for off-heap memtables. Should be use the same option or add
> another?
> memory_allocator: JEMallocAllocator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
