[
https://issues.apache.org/jira/browse/CASSANDRA-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230421#comment-15230421
]
Michael Shuler commented on CASSANDRA-11514:
--------------------------------------------
[trunk_3.5_3.0-compaction_LCS|http://cstar.datastax.com/tests/artifacts/7b642270-fccc-11e5-bf65-0256e416528f/graph]
shows that both trunk and 3.5 seem to have the same issue. 'op rate' text and
'Total operations' graph seem to agree.
[trunk_3.5_3.0-compaction_DTCS|http://cstar.datastax.com/tests/artifacts/2aace7d6-fccc-11e5-bf65-0256e416528f/graph]
is less conclusive.
I'm going to run both for a longer period and write more data to see if I can
get a little more definitive answer.
> trunk compaction performance regression
> ---------------------------------------
>
> Key: CASSANDRA-11514
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11514
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: cstar_perf
> Reporter: Michael Shuler
> Labels: performance
> Fix For: 3.x
>
> Attachments: trunk-compaction_dtcs-op_rate.png,
> trunk-compaction_lcs-op_rate.png
>
>
> It appears that a commit between Mar 29-30 has resulted in a drop in
> compaction performance. I attempted to get a log list of commits to post
> here, but
> {noformat}
> git log trunk@{2016-03-29}..trunk@{2016-03-31}
> {noformat}
> appears to be incomplete, since reading through {{git log}} I see netty and
> och were upgraded during this time period.
> !trunk-compaction_dtcs-op_rate.png!
> !trunk-compaction_lcs-op_rate.png!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
