cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4338) Experiment with direct buffer in SequentialWriter
Date Mon, 07 Oct 2013 18:03:43 GMT

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

Ryan McGuire commented on CASSANDRA-4338:
-----------------------------------------

I started to run a benchmark for this but I found CASSANDRA-6153 and CASSANDRA-6154 standing
in my way.

[Here's the data|http://ryanmcguire.info/ds/graph/graph.html?stats=stats.4338.CompressedSequentialWriter.json&metric=interval_op_rate&operation=stress-write&smoothing=4]
for my test with [~krummas]' patch, but it's missing any sort of baseline because of those
above bugs. 

> 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-gc.tar.gz, 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)

Mime
View raw message