cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Zhuang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-12676) Message coalescing regression
Date Sat, 10 Dec 2016 07:05:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737380#comment-15737380
] 

Jay Zhuang edited comment on CASSANDRA-12676 at 12/10/16 7:05 AM:
------------------------------------------------------------------

[~jjirsa] one comment on the patch:
In 2.2, the default value for otc_coalescing_strategy is actually 'TIMEHORIZON'. It was disabled
*before* 2.2.


was (Author: jay.zhuang):
[~jjirsa] comment on the patch:
In 2.2, the default value for otc_coalescing_strategy is actually 'TIMEHORIZON'. It was disabled
*before* 2.2.

> 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: 4.0, 3.x
>
>         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.3.4#6332)

Mime
View raw message