[ https://issues.apache.org/jira/browse/CASSANDRA-11514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260406#comment-15260406 ]
Michael Shuler commented on CASSANDRA-11514: -------------------------------------------- I was unable to find a concrete method to bisect this - I attempted a good number of variations to find a way to call a commit "good" or "bad", but was unsuccessful. Those are on a private jira [CSTAR-478|https://datastax.jira.com/browse/CSTAR-478], which I'm going to close, since I'm currently unsure of how to proceed. > 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)