[
https://issues.apache.org/jira/browse/CASSANDRA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125081#comment-14125081
]
Jay Patel commented on CASSANDRA-7883:
--------------------------------------
There're two NativeAllocator.java classes in codebase:
/cassandra-trunk/src/java/org/apache/cassandra/io/util/NativeAllocator.java =>
Wrapper on native gcc allocator
/cassandra-trunk/src/java/org/apache/cassandra/utils/memory/NativeAllocator.java
=> Slab Allocator for off-heap objects/memtable. It can underneath use
NativeAllocator or JEMalloc or something else based on the "memory_allocator"
property. Should we refactor this to a better name?
will take care of refactoring as part of another tix, if it makes sense.
> 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
> 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)
