[
https://issues.apache.org/jira/browse/CASSANDRA-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795422#comment-15795422
]
Ariel Weisberg commented on CASSANDRA-13090:
--------------------------------------------
Right but we don't need the network to coalesce for us since we are already
doing it. But... there isn't a motivation to coalesce more than some number of
messages. All it's going to do is add latency with minimal reduction in
overhead.
I see I understood limit incorrectly. It might be clearer as now + nano / 16
and some parens for those of us a bit weaker at math.
> Coalescing strategy sleep too much
> ----------------------------------
>
> Key: CASSANDRA-13090
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13090
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Corentin Chary
> Fix For: 3.x
>
> Attachments: 0001-Fix-wait-time-coalescing-CASSANDRA-13090.patch
>
>
> With the current code maybeSleep is called even if we managed to take
> maxItems out of the backlog. In this case we should really avoid sleeping
> because it means that backlog is building up.
> I'll send a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
