cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9240) Performance issue after a restart
Date Fri, 08 May 2015 03:03:01 GMT

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

Stefania commented on CASSANDRA-9240:
-------------------------------------

Thanks for this. I see the mean latency on read doubles after restart on trunk, is this expected?


On the 8897 branch it's even worse, it's already double that of trunk on the first read and
it degrades further after a restart so I definitely did something wrong which I'll have to
work out but I'll carry on the discussion on that ticket.

Here are the results in case anyone is interested.

{code}
Mean latency (one none running in foreground with -Xms500M -Xmx500M -Xmn50M, inserting 200k
and reading back 50k):

TRUNK insert 7.2
TRUNK read 8.7
TRUNK read after restart 16.4

8897 insert 6.8
8897 read 16.6
8897 read after restart 22.3
{code}

> Performance issue after a restart
> ---------------------------------
>
>                 Key: CASSANDRA-9240
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9240
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 3.x
>
>         Attachments: Cassandra.snapshots.zip, cassandra_2.1.4-clientrequest-read.log,
cassandra_2.1.4.log, cassandra_2.1.5-clientrequest-read.log, cassandra_2.1.5.log, cassandra_trunk-clientrequest-read.log,
cassandra_trunk.log, cassandra_trunk_no_restart-clientrequest-read.log, cassandra_trunk_no_restart.log,
issue.yaml, run_issue.sh, runs.log, trace_query.cql
>
>
> I have noticed a performance issue while I was working on compaction perf tests for CASSANDRA-7409.
The performance for my use case is very bad after a restart. It is mostly a read performance
issue but not strictly. I have attached my use case (see run_issue.sh and issue.yaml) and
all test logs for 2.1.4, 2.1.5 and trunk:
> * 2.1.* are OK (although 2.1.4 seems to be better than 2.1.5?): ~6-7k ops/second and
~2-2.5k of read latency.  
> * trunk is NOT OK: ~1.5-2k ops/second and 25-30k of read latency.
> * trunk is OK without a restart: ~ same perf than 2.1.4 and 2.1.5.
> EDIT: branch cassandra-2.1 is OK.
> I can help to bisect and/or profile on Monday if needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message