cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5933) 2.0 read performance is slower than 1.2
Date Tue, 03 Sep 2013 02:46:51 GMT

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

Vijay commented on CASSANDRA-5933:
----------------------------------

Ryan, Do you mind testing the custom with 5 to 10 ms... 
I am thinking, we might need enough sample for Percentiles to make more sense (if conformed
we might want to wait till the samples arrive etc).
                
> 2.0 read performance is slower than 1.2
> ---------------------------------------
>
>                 Key: CASSANDRA-5933
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5933
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ryan McGuire
>         Attachments: 1.2-faster-than-2.0.png, 1.2-faster-than-2.0-stats.png
>
>
> Over the course of several tests I have observed that 2.0 read performance is noticeably
slower than 1.2
> Example:
> Blue line is 1.2, the rest are various forms of 2.0 rc1 (I've also seen this on rc2,
just don't have a good graph handy)
> !1.2-faster-than-2.0.png!
> !1.2-faster-than-2.0-stats.png!
> [See test data here|http://ryanmcguire.info/ds/graph/graph.html?stats=stats.eager_retry.node_killed.json&metric=interval_op_rate&operation=stress-read&smoothing=1]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message