[
https://issues.apache.org/jira/browse/CASSANDRA-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968960#comment-13968960
]
Vijay edited comment on CASSANDRA-7030 at 4/14/14 10:52 PM:
------------------------------------------------------------
Not enough iterations i guess....
Just ran the old tool again (to verify if i am still making sense :) ) and i do
get the same kind of results (http://pastebin.com/LPFUutaY)...
Things might be different like the kernel version etc.... Also there is no
difference in the allocator except the malloc is over written to do threaded
allocation you can see bench marks online too.
was (Author: vijay2...@yahoo.com):
Not enough iterations i guess....
Just ran the old tool again (to verify if i am still making sense :) ) and i do
get the same kind of results (http://pastebin.com/LPFUutaY)...
Things might be different like the kernel version etc.... Also there is no
difference in the allocator except the malloc is over written to do threaded
allocation you can see bench marks inline too.
> 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)
