cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7030) Remove JEMallocAllocator
Date Mon, 14 Apr 2014 13:56:15 GMT

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

Jason Brown commented on CASSANDRA-7030:
----------------------------------------

[~vijay2win@yahoo.com] Vijay, you might have an interest in this one.

> Remove JEMallocAllocator
> ------------------------
>
>                 Key: CASSANDRA-7030
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7030
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>              Labels: performance
>             Fix For: 2.1 beta2
>
>         Attachments: 7030.txt
>
>
> JEMalloc, whilst having some nice performance properties by comparison to Doug Lea's
standard malloc algorithm in principle, is pointless in practice because of the JNA cost.
In general it is around 30x more expensive to call than unsafe.allocate(); malloc does not
have a variability of response time as extreme as the JNA overhead, so using JEMalloc in Cassandra
is never a sensible idea. I doubt if custom JNI would make it worthwhile either.
> I propose removing it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message