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 Thu, 26 Feb 2015 19:30:06 GMT

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

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

bq. change to MemoryUtil.setBytes

Just changed that in order to remove an unsafe call. In the end it shouldn't make any difference
since both access the same thing (esp. after hotspot did its job).

> 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-2.txt, 8714-3.txt, 8714-4.txt, 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