[
https://issues.apache.org/jira/browse/CASSANDRA-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968515#comment-13968515
]
Vijay commented on CASSANDRA-7030:
----------------------------------
Hi Bendict,
Interesting how slow is slow in terms of Cassandra's throughput/latencies?
Isn't it tradeoff between memory fragmentation (use) vs speed?
here is the test for memory footprint
https://issues.apache.org/jira/browse/CASSANDRA-3997?focusedCommentId=13243924&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13243924
> 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)
