[jira] [Commented] (CASSANDRA-18104) Major Performance degradation of Casandara 4.0.7 against Casandra 3.11.14

["Brandon Williams (Jira)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-18104:
----------------------------------------------

I created the keyspace simply: CREATE KEYSPACE mailbox WITH replication = {'class': 'SimpleStrategy', 'replication_factor': '1'} 

For 4.0 I had to remove the read repair parameters from schema.cql since they are deprecated.  I first warmed up the JVM by running the query30.txt through cqlsh 100 times.

3.11:
{noformat}
drift@focal1:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m4.854s
user    0m4.471s
sys     0m0.100s
drift@focal1:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m4.766s
user    0m4.420s
sys     0m0.111s
drift@focal1:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m4.876s
user    0m4.561s
sys     0m0.085s
{noformat}

4.0:
{noformat}
drift@focal2:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m3.952s
user    0m3.720s
sys     0m0.110s
drift@focal2:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m4.050s
user    0m3.832s
sys     0m0.100s
drift@focal2:~/cassandra$ time bin/cqlsh -f query30.txt > /dev/null

real    0m4.067s
user    0m3.846s
sys     0m0.099s
{noformat}

This isn't the most scientific test since there's also the time to fork python, but 4.0 is consistently faster.

> Major Performance degradation of  Casandara 4.0.7   against Casandra 3.11.14
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18104
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18104
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sreedhar J
>            Priority: Urgent
>         Attachments: 3.11.14.txt, 4.0.7.txt, mailboxes_snapshot.zip, query30.txt
>
>
> Our application uses Casandra 3.11.x  and has lot of security vulnerabilities  which are addressed in 4.0.x.  So  we have upgraded the Casandra to 4.0.7 and  our performance tests have shown aorund 20% degradation  compare to 3.11.x    
> We are now able to reproduce the same performance degradation using the standalone queries.   Here are the steps.
> 1. Expand Cassandra 3.11.14 tarball and 4.0.7 tarball to different folders
> 2. Import the attached data from the snapshot (mailboxes_snapshot.zip) into each Cassandra instance, see schema.cql for CQL for creating the required table and indexes before import
> 3. With CQLSH run the following query several times with TRACING ON and PAGING OFF against both versions of Cassandra:  select * from mailbox.mailboxes where mbx_id= 6c57da2e-7ddd-4984-be62-105415e6b48a;
> 4. Compare results
> IWe ran the target query 30 times. Here's the average times to run the query:
> 3.11.14 - 19400.77
> 4.0.7 - 34906.03



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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