[
https://issues.apache.org/jira/browse/CASSANDRA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125201#comment-14125201
]
Benedict commented on CASSANDRA-7883:
-------------------------------------
We don't tend to file tickets for that kind of discussion - can try having it
on IRC #cassandra.
Largely I chose NativeAllocator as a name because it was the simplest and
cleanest name, which kept cleaner all code areas that refer to it.
OffHeapObjectSlabAllocator is much too ugly/long. OffHeapAllocator was the
first name I used, but I opted to change it because I felt that was also longer
than necessary.
> 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: 3.0
>
> 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 we use the same option or add
> another?
> memory_allocator: JEMallocAllocator
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
