You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/08/11 20:38:46 UTC

[jira] [Commented] (CASSANDRA-4338) Experiment with direct buffer in SequentialWriter

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

Jonathan Ellis commented on CASSANDRA-4338:
-------------------------------------------

Is this obsoleted by CASSANDRA-9500?

> Experiment with direct buffer in SequentialWriter
> -------------------------------------------------
>
>                 Key: CASSANDRA-4338
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4338
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Branimir Lambov
>            Priority: Minor
>              Labels: performance
>             Fix For: 2.1.x
>
>         Attachments: 4338-gc.tar.gz, 4338.benchmark.png, 4338.benchmark.snappycompressor.png, 4338.single_node.read.png, 4338.single_node.write.png, gc-4338-patched.png, gc-trunk-me.png, gc-trunk.png, gc-with-patch-me.png
>
>
> Using a direct buffer instead of a heap-based byte[] should let us avoid a copy into native memory when we flush the buffer.



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