[
https://issues.apache.org/jira/browse/CASSANDRA-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-821:
---------------------------------------
Description: 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. (was: 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 defaults, and latency is
300-500ms.)
> get_range_slice performance
> ---------------------------
>
> Key: CASSANDRA-821
> URL: https://issues.apache.org/jira/browse/CASSANDRA-821
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7
> Reporter: Brandon Williams
> Priority: Minor
>
> 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.
