[
https://issues.apache.org/jira/browse/CASSANDRA-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338990#comment-14338990
]
Ariel Weisberg commented on CASSANDRA-8714:
-------------------------------------------
I guess? I'm not brave enough to assume it's going to be able to figure out
that in all cases at that call site there will only be DirectByteBuffers. That
particular line will only ever be invoked with DirectByteBuffers, but the
surrounding method will have both so I don't know what information the compiler
is going to have to deduce that.
You could run with print inlining and a single call site for setBytes and pass
in randomly a direct/non-direct buffer and see if it is inlined.
> 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)
