I saw this in the todo list for jgroups anonymous wrote : | - FC: on a fast network, we can still run out of memory because received_msgs/delivered_msgs becomes very big. | Instead of basing FC on the speed of the network, we should also take the number of messages processed | (a.k.a delivered_msgs/received_msgs) into account, and only send credits when that number falls below a | certain threshold. First: look at the number of received/delivered msgs in the perf test ! | --> Look into memory-based FC: criteria for sending credits are | - available free memory | - outstanding retransmission requests (sender sends with each message number of messages sent, | receiver keeps track of how many messages received, if diff is > threshold --> pause) | - [optional] latency
any plans of implementing this ? cause this might be the problem. or is there any other flow control protocol that i could try. Also is there a doc which explains the various parameters that one can tweak in jgroup. Thank You ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909641#3909641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909641 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
