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 Tue, 08 Oct 2013 21:32:44 GMT

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

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

And I notice that the marcuse/4338 line still doesn't have latency metrics, if you'd like
me to re-run for those stats, I can. Just need to rebase off of CASSANDRA-6153 (or rewrite
my tool to use a known good cassandra-stress; right now it just takes the one from the same
branch it's testing.)

> 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-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