[Spread-users] spread performance looks not very good for me

Ryan Caudy caudy at jhu.edu
Fri Dec 5 21:06:04 EST 2003

I don't have a decent Solaris cluster to test on, but a quick test using 
our Linux cluster (on a 100 Mbps ethernet network) gives (pretty rough) 
results of:

1 sender + 1 receiver:	85 Mbps
1 sender + 2 receivers:	40 Mbps
3 senders:		52 Mbps

In each of these tests, nodes listed as senders are receiving messages 
as well, and nodes listed as receivers are just receiving.  Having more 
sending nodes will increase the overall throughput, because more of the 
token's circulation time will be used to send.  I'm not sure of the 
details of the test that led to the 8000 * 1KB number on the Spread 

I think the problem may lie outside of Spread, or with the Solaris port.


wei_hu at agilent.com wrote:

> Spread performance question:
> I am doing some investigation on spread to decide if it could be used as middleware in our project.  I studied spread for two days and did some benchmark.  I do have some questions.  Appreciate any comment on them.
> To do the benchmark, I used one Solaris machine as Sender and other one/two machines as Receivers.  All machines are in one subnet. Spfloor in spread package was used as benchmark program.  There is average message rate I got.  Message size was 1K.
> 1 sender + 1 receiver: 19.07 Mbps
> 1 sender + 2 receiver: 13.46 Mbps
> The sender and one of the receivers is 500Mhz CPU, 1G memory, Solaris OS.  Another receiver is 500Mhz CPU, 512M memory, Solaris OS.
> My question is:
> 1.	The message transmitting rate is far below what is claimed in "Spread Overview" (8K 1Kbytes per second).  Any possible reason for that?
> 2.	Why plugging in more receivers decreased the message transmitting rate?
> 3.	Spread daemon burned up to 70% CPU time?
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users

Ryan W. Caudy
Center for Networking and Distributed Systems
Department of Computer Science
Johns Hopkins University

More information about the Spread-users mailing list