[
https://issues.apache.org/jira/browse/CASSANDRA-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa resolved CASSANDRA-10327.
------------------------------------
Resolution: Won't Fix
Seems unlikely we'll be addressing a 2.2 regression anymore, especially with a
suspect 2.1 test. I'm reasonably sure you won't mind, [~benedict] , but if I'm
wrong and you do care, please let me know.
> Performance regression in 2.2
> -----------------------------
>
> Key: CASSANDRA-10327
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10327
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benedict
> Fix For: 2.2.x
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
