[
https://issues.apache.org/jira/browse/CASSANDRA-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229806#comment-15229806
]
Branimir Lambov commented on CASSANDRA-4338:
--------------------------------------------
Switch to byte buffers, and making a direct/on-heap choice that makes best
sense for the subclass or compressor was implemented as part of CASSANDRA-8709,
which is included in 2.2.
The issue is now obsolete, unless we want to backport the patch to 2.1.
> Experiment with direct buffer in SequentialWriter
> -------------------------------------------------
>
> Key: CASSANDRA-4338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4338
> Project: Cassandra
> Issue Type: Improvement
> Components: Local Write-Read Paths
> 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)
