You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2016/05/02 20:39:13 UTC
[jira] [Commented] (CASSANDRA-11514) trunk compaction performance
regression
[ https://issues.apache.org/jira/browse/CASSANDRA-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267232#comment-15267232 ]
Marcus Eriksson commented on CASSANDRA-11514:
---------------------------------------------
What are we measuring here? Write performance or compaction performance? The graph looks like it is write perf?
> 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)