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

David Capwell commented on CASSANDRA-16078:
-------------------------------------------

used tlp-stress but can't share the test code, though can explain it enough to 
reproduce.

// create
{code}
CREATE TABLE IF NOT EXISTS clusteringslicing (
  key         text,
  column1     bigint,
  value       blob,
  PRIMARY KEY(key, column1)
) WITH CLUSTERING ORDER BY (column1 DESC)
{code}

// select
{code}
SELECT key, column1
 FROM clusteringslicing
 WHERE key = ?
   AND column1 >= ?
   AND column1 <= ?
 LIMIT ?
{code}

// test configs
{code}
limit == 100
max_blob_length=102400
rows_per_partition=1000
use_range_tombstones=false
LeveledCompactionStrategy
num_partitions=1000
duration="60m"
delete_rate=0.11
read_rate=0.11
{code}

when selecting the clustering key bounds, the test uses a uniform distribution 
between 0 and rows_per_partition

Hope this helps!

Its been a while since I ran the test, if desired I can rerun again to see if 
anything has changed.

> 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
>            Priority: Normal
>             Fix For: 4.0-beta
>
>         Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to