Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <1712152431.3701270802870776.JavaMail.jira@brutus.apache.org>
Date: Fri, 9 Apr 2010 08:47:50 +0000 (UTC)
From: "Johan Oskarsson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-821) get_range_slice performance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Johan Oskarsson commented on CASSANDRA-821:
-------------------------------------------

Works for me. +1

> get_range_slice performance
> ---------------------------
>
>                 Key: CASSANDRA-821
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-821
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Brandon Williams
>            Assignee: Johan Oskarsson
>            Priority: Minor
>             Fix For: 0.7
>
>         Attachments: 821-v2-diff.txt, 821-v2.txt, CASSANDRA-821.patch, CASSANDRA-821.patch, CASSANDRA-821.patch, CASSANDRA-821.patch
>
>
> get_range_slice performance isn't that great.  CASSANDRA-799 helped in the case when the memtable isn't flushed, but overall the operations per second and latency is still pretty bad.  On a quad core node with a trivial amount of data I see around 130-150 ops per second with stress.py set to slice 100 keys at a time, and latency is 300-500ms.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.