[
https://issues.jboss.org/browse/JGRP-1717?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1717:
--------------------------------
Investigate idea by [~rvansa]:
As a last thought for DefaultBundler2 principle (this is the one I find most appealing):
It seems to me that the thread does not do much work in the lock, so the bundle does not
grab much messages. The format of batch does not specify how many messages will there be
in advance, so, instead of just adding the message to list (fast), couldn't we keep
the DataOutputStream and write the message to the stream?
Potential issues:
* We don't know up front whether the batch has 1 or more messages; in case of 1
message we send a single message, otherwise we send a batch. However, the wire format is
different
* We'd have to associate one output stream per target destination
Bundling reduces performance in scenario mimicking Inifinispan
--------------------------------------------------------------
Key: JGRP-1717
URL:
https://issues.jboss.org/browse/JGRP-1717
Project: JGroups
Issue Type: Bug
Affects Versions: 3.3
Reporter: Radim Vansa
Assignee: Bela Ban
Fix For: 3.5
Attachments: benchmark-jgroups.xml, jgroups-udp.pdf, jgroups-udp.xml
In Radargun benchmark of JGroups mimicking the behaviour of Infinispan we can see that
performance with bundling on actually reduces the performance.
See attached configurations and results.
--
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