[jboss-jira] [JBoss JIRA] (JGRP-2024) Receiving messages out of order.

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-2024:
--------------------------------

Sample configs {{udp-largecluster.xml}} and {{fast.xml}} are starting points, but this largely depends on what you want to do. Is it more Infinispan style traffic? Then UPerf is a good test, otherwise MPerf might be useful.
I'd start the tuning process at the transport level and size the 2 thread pools accordingly. For example, if you disable the queue in the regular pool and up the max size, you'll get more concurrency. But again, it depends on 
* How many senders do you have?
* Cluster size
* Regular or OOB messages?
* Blocking or non-blocking RPCs

Further things to look at:
* Can you compress data? -> {{COMPRESS}}
* Flow control; possibly increase credits
* UDP or TCP as transport?
* Message batching (JGroups 4.0)
* Type of message bundler in the transport
* Run perf test and use probe to measure stats and adapt config
* etc etc etc

These are things we discuss in the workshop [1].
[1] http://www.jgroups.org/workshops.html

> Receiving messages out of order.
> --------------------------------
>
>                 Key: JGRP-2024
>                 URL: https://issues.jboss.org/browse/JGRP-2024
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.6.7, 3.6.8
>         Environment: RedHat 6.7
> Java 1.8.0 Update 45
>            Reporter: Dylan Turnbull
>            Assignee: Bela Ban
>             Fix For: 4.0
>
>         Attachments: jGroups Unit Test.zip, JGroupsMessageTest.java, jGroupsTestReciever.java
>
>
> After splitting a file into smaller messages and send them down the channel the messages are received on the other side out of order.
> Below is a sample output:
> *+On the sender:+*
> Sending...
> Data Sent:
> Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy te
> -----------------------------------------------------
> Data Sent:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Sent:
> vived not only five centuries, but also the leap into electronic typesetting, re
> -----------------------------------------------------
> Data Sent:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passag
> *+On the receiver:+*
> Listening...
> Data Received:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Received:
> vived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularise
> -----------------------------------------------------
> Data Received:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)