cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-10327) Performance regression in 2.2
Date Fri, 22 Sep 2017 04:25:00 GMT


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:
>             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
> The query is looking up the last item of a partition.
> [run1|]
> [run2|]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message