You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2021/01/14 18:58:01 UTC

[jira] [Comment Edited] (CASSANDRA-16078) Performance regression for queries accessing multiple rows

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

Caleb Rackliffe edited comment on CASSANDRA-16078 at 1/14/21, 6:57 PM:
-----------------------------------------------------------------------

I'm planning on taking a look at this starting early next week at the latest.

Given that everything here seems partition-restricted, I'm inclined to strip things down to some single-node read comparisons, and I have David's original test scripts at my disposal...


was (Author: maedhroz):
I'm planning on taking a look at this starting early next week at the latest.

Given that everything here seems partition-restricted, I'm inclined to strip things down to some single node read comparisons, and I have David's original test scripts at my disposal...

> Performance regression for queries accessing multiple rows
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-16078
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16078
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Coordination
>            Reporter: David Capwell
>            Assignee: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 4.0-beta
>
>         Attachments: ClusteringSlicing.kt, image.png
>
>
> This is spin off from CASSANDRA-16036.
> In testing 4.0 relative to 3.0* I found that queries which accessed multiple rows to have a noticeable performance decrease; two queries were used in the test (more may be impacted, others might not): query partition (table has clustering keys) with LIMIT, and query clustering keys using IN clause.
> In the below graphs the green line is 3.0 and the other lines are 4.0 (with and without chunk cache)
> Partition with LIMIT
> !https://issues.apache.org/jira/secure/attachment/13009751/clustering-slice_latency_selects_baseline.png!
> !https://issues.apache.org/jira/secure/attachment/13009750/clustering-slice_latency_under90_selects_baseline.png!
> Cluster with IN clause
> !https://issues.apache.org/jira/secure/attachment/13009749/clustering-in-clause_latency_selects_baseline.png!
> !https://issues.apache.org/jira/secure/attachment/13009748/clustering-in-clause_latency_under90_selects_baseline.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org