cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9240) Performance issue after a restart
Date Fri, 01 May 2015 20:40:09 GMT


Benedict commented on CASSANDRA-9240:

Well now that really doesn't make sense, since it should do nothing without mmap. It won't
open/close the channel, since that's wrapped by the SegmentedFile, and it uses a heap buffer,
so it cannot waste time cleaning it....

> Performance issue after a restart
> ---------------------------------
>                 Key: CASSANDRA-9240
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 3.x
>         Attachments:, 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,, 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 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

View raw message