You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2015/01/28 21:10:35 UTC
[jira] [Commented] (CASSANDRA-8692) Coalesce intra-cluster network
messages
[ https://issues.apache.org/jira/browse/CASSANDRA-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295754#comment-14295754 ]
Ariel Weisberg commented on CASSANDRA-8692:
-------------------------------------------
Commits are on github https://github.com/aweisberg/cassandra/compare/C-8692?expand=1
I left the buffer size for IncomingTcpConnection alone although it is configurable in a pinch. I increased OutboundTcpConnections buffer size to 64 kilobytes. I think the right default needs more research.
I want to make a unit test for the rest of OutboundTcpConnection. I am still figuring out the right way to do that.
> Coalesce intra-cluster network messages
> ---------------------------------------
>
> Key: CASSANDRA-8692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8692
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
>
> While researching CASSANDRA-8457 we found that it is effective and can be done without introducing additional latency at low concurrency/throughput.
> The patch from that was used and found to be useful in a real life scenario so I propose we implement this in 2.1 in addition to 3.0.
> The change set is a single file and is small enough to be reviewable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)