[ https://issues.apache.org/jira/browse/CASSANDRA-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791713#comment-13791713 ]
Ryan McGuire commented on CASSANDRA-4338: ----------------------------------------- On a single node: !4338.single_node.write.png! The read was weird, I don't know what that spike is. I'm rerunning this to see if it does it again: !4338.single_node.read.png! > 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: Marcus Eriksson > Priority: Minor > Labels: performance > Fix For: 2.1 > > Attachments: 4338.benchmark.png, 4338.benchmark.snappycompressor.png, > 4338-gc.tar.gz, 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.1#6144)