You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/09/05 11:23:28 UTC

[jira] [Commented] (CASSANDRA-7883) Allow plugging JEMalloc for off-heap memtables

    [ https://issues.apache.org/jira/browse/CASSANDRA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122714#comment-14122714 ] 

Benedict commented on CASSANDRA-7883:
-------------------------------------

I'm not convinced by the necessity of this, if only because we allocate in large-ish quantities so there's not likely to be any measurable impact. That said, it's also trivial and no downside, so happy to include if you post a patch.

> 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
>             Fix For: 2.1.1
>
>
> 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)