[jboss-jira] [JBoss JIRA] (JGRP-1662) Remove flow control and fragmentation if run on TCP transport

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790934#comment-12790934 ] 

Bela Ban commented on JGRP-1662:
--------------------------------

One reason the TCP-based config performs worse lies in the design of the transport: a received message is passed to a thread pool, which might discard it if full, but the TCP receive() never blocks. Therefore, TCP's flow control continues sending full steam ahead and never throttles the sender, leading to overflow at the receiver.
Adding MFC back re-establishes flow control and thus throttles the sender.
                
> 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