Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 9 Oct 2013 10:17:49 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12560558.1339621361680.37527.1381313869915@arcas>
In-Reply-To: <JIRA.12560558.1339621361680@arcas>
References: <JIRA.12560558.1339621361680@arcas>
Subject: [jira] [Commented] (CASSANDRA-4338) Experiment with direct buffer
 in SequentialWriter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marcus Eriksson commented on CASSANDRA-4338:
--------------------------------------------

yep, that looks very similar

did you run it with -I SnappyCompressor ?

ive rebased and (force) pushed to https://github.com/krummas/cassandra/tree/marcuse/4338 to get the latency stuff in

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