cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4338) Experiment with direct buffer in SequentialWriter
Date Thu, 10 Oct 2013 14:34:45 GMT

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

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

Ryan, can you also test on a single node?

If the single-node improvements are still swamped by the network overhead...  but if we can
reduce that with some of the other efforts going on (CASSANDRA-1632, CASSANDRA-4718) then
local performance will matter more.

But if Ryan doesn't see much difference on a single node either then we should figure out
what the environment difference is.

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