You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2015/09/14 21:06:45 UTC

[jira] [Created] (CASSANDRA-10327) Performance regression in 2.2

Benedict created CASSANDRA-10327:
------------------------------------

             Summary: Performance regression in 2.2
                 Key: CASSANDRA-10327
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10327
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Benedict
             Fix For: 2.2.2


Related to CASSANDRA-10326, one of the read-only workloads _appears_ to show a regression in 2.2, however it is possible this is simply down to a different compaction result (this shouldn't be very likely given the use of LCS, though, and that we wait for compaction to acquiesce, and while the different is not consistent across both runs, it is consistently worse).

The query is looking up the last item of a partition.

[run1|http://cstar.datastax.com/graph?stats=f0a17292-5a13-11e5-847a-42010af0688f&metric=op_rate&operation=3_user&smoothing=1&show_aggregates=true&xmin=0&xmax=155.43&ymin=0&ymax=13777.5]
[run2|http://cstar.datastax.com/graph?stats=e25aaaa0-5a13-11e5-ae0d-42010af0688f&metric=op_rate&operation=3_user&smoothing=1&show_aggregates=true&xmin=0&xmax=74.36&ymin=0&ymax=34078]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)