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-821) get_range_slice performance
Date Tue, 30 Mar 2010 21:40:27 GMT

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

Jonathan Ellis commented on CASSANDRA-821:
------------------------------------------

With CASSANDRA-917 in, what I'd like to see in 821 is a layer (part of QueryFilter?  a separate
class?) that provides an Iterator<Row>, from a bunch of sstables and memtables, the
way QF provides ColumnIterators.  (You would get each Row from a key + ColumnFamily, and each
CF from a group of ColumnIterators.)

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


Mime
View raw message