[jboss-jira] [JBoss JIRA] (JGRP-1662) Remove flow control and fragmentation if run on TCP transport
Bela Ban (JIRA)
jira-events at lists.jboss.org
Fri Jul 19 04:59:27 EDT 2013
[ https://issues.jboss.org/browse/JGRP-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790930#comment-12790930 ]
Bela Ban commented on JGRP-1662:
--------------------------------
Changed thread pool config: a high queue size led to a high number of 70k messages getting queued, which was the reason for the OOMEs. Adjusted min_size to 4 and set the queue size to 1000. However, numbers went up to 79MB/sec/node, compared to 87MB/sec/node for the old config (+MFC +FRAG2).
> Remove flow control and fragmentation if run on TCP transport
> -------------------------------------------------------------
>
> Key: JGRP-1662
> URL: https://issues.jboss.org/browse/JGRP-1662
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3.4, 3.4
>
>
> When run with a TCP transport, we don't need MFC and FRAG(2). However, if we remove FRAG2, the bundler at the transport will drop a message if it exceeds max_bundle_size.
> Let's therefore bypass message bundling when the transport is TCP (TCP has its own batching).
> TODO: measure how this change affects performance on a 4 node cluster. If positive, commit it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list