cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8714) row-cache: use preloaded jemalloc w/ Unsafe
Date Sat, 07 Feb 2015 08:50:35 GMT

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

Robert Stupp commented on CASSANDRA-8714:
-----------------------------------------

I just wanted to benchmark allocation performance - and not accessing memory since that would
add a constant overhead to the comparison. Maybe it would also add some "negative" value to
the bigger systems (c3/c4).

But this is an artificial benchmark. To benchmark a "real scenario" I'd had to allocate more
memory, keep memory allocated, use different allocation sizes and so on. IMO that's too heavy
for a JMH.

Yea - maybe it's really the thing that JNI is more optimized.

> row-cache: use preloaded jemalloc w/ Unsafe
> -------------------------------------------
>
>                 Key: CASSANDRA-8714
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8714
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>             Fix For: 3.0
>
>         Attachments: 8714.txt
>
>
> Using jemalloc via Java's {{Unsafe}} is a better alternative on Linux than using jemalloc
via JNA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message