[
https://issues.apache.org/jira/browse/CASSANDRA-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129162#comment-16129162
]
Mike Bulman commented on CASSANDRA-12676:
-----------------------------------------
Thoughts on removing 3.0.12 from Fix Version, to make life easier for our
future selves, since the default was not changed there? That was my initial
assumption before reading all of the comments and confirming through git
spelunking
> Message coalescing regression
> -----------------------------
>
> Key: CASSANDRA-12676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12676
> Project: Cassandra
> Issue Type: Bug
> Reporter: T Jake Luciani
> Assignee: Jeff Jirsa
> Labels: docs-impacting
> Fix For: 3.0.12, 3.11.0, 4.0
>
> Attachments: 12676.diff, coalescing_disabled.png, result.html
>
>
> The default in 2.2+ was to enable TIMEHORIZON message coalescing. After
> reports of performance regressions after upgrading from 2.1 to 2.2/3.0 we
> have discovered the issue to be this default.
> We need to re-test our assumptions on this feature but in the meantime we
> should default back to disabled.
> Here is a performance run [with and without message
> coalescing|http://cstar.datastax.com/graph?command=one_job&stats=9a26b5f2-7f48-11e6-92e7-0256e416528f&metric=op_rate&operation=2_user&smoothing=1&show_aggregates=true&xmin=0&xmax=508.86&ymin=0&ymax=91223]
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
