FW: Re: [Spread-users] Spread Performance

[Ryan Caudy]

Please send your configuration file to the list.

--Ryan

William Isley wrote:

> I am headed down the path of using a separate Spread Daemon for each 
> individual group messager. I still don't get the performance I need 
> however. I plan to tweek the token passing timeouts and message 
> buffersizes of the daemon.
> 
> I am having a problem running the spmonitor. First, I did not see a 
> project file to build this under Windows, so I created one. When I run 
> the monitor I get the following error:
> 
> Conf_init: using file: spread.conf
> DL_init_channel: socket error for port 6543
> Exit caused by Alarm(EXIT)
> 
> The command I used to run the monitor is spread -n Machine5 where 
> Machine5 is defined as the Spread Daemon running on the local machine in 
> spread.conf. I tried telling the monitor to use port 4803, but this did 
> not resolve the issue. I have dangerous messages enabled in the 
> spread.conf file.
> 
> I am trying to run the monitor against a Spread Daemon running on local 
> host. Does anyone know why I get this error?
> 
> William
> 
> 
>> From: John Schultz <jschultz at spreadconcepts.com>
>> To: "spread-users at lists.spread.org" <spread-users at lists.spread.org>
>> Subject: Re: FW: Re: [Spread-users] Spread Performance
>> Date: Wed, 28 Apr 2004 12:34:07 -0400
>>
>> Ciprian Tutu wrote:
>>
>>> Hi,
>>>
>>> WI> I configured 3 machines, over 100Mbit Ethnet, each PIIIs running 
>>> Windows XP
>>> WI> (yes, I know evil Microsoft). 2 machines I configured with Spread 
>>> Daemons
>>> WI> with apps I wrote implimenting the Spread API to receive 
>>> messages. 1 machine
>>> WI> served as a message sender and connected to one of the other 
>>> machines Spread
>>> WI> Daemons.
>>>
>>> Honestly I would configure one daemon on each of your 3 machines and 
>>> have
>>> each client application (including the sender) connect to their local
>>> daemon. This way you really let spread handle _all_ the traffic of the
>>> experiment.
>>>
>>> Add your 3rd daemon to the config file on each machine and give it a
>>> try.
>>>
>>
>> I agree with this recommendation.  You really want Spread running on 
>> every machine with processes that could call SP_connect.  Usually your 
>> SP_connect call should be a hardcode to <port_num>@localhost.
>>
>> Another thing to check is whether or not your configuration is losing 
>> messages at all.  If the network is losing tokens intermittently but 
>> often this would slow you down.  You can detect this by examining the 
>> state of all the daemons using spmonitor and looking at the retrans 
>> fields.  If these numbers are in the hundreds or thousands, then you 
>> have a lossy network or NICs and need to fix that.
>>
>> Regardless, in recent experiments that we have run on Spread using 
>> Windows in small configurations we couldn't do much better than 40Mb 
>> (5MB) / sec.  We believe that Spread's event system on Windows' 
>> doesn't perform as well as it does on *nix.  We were trying to fix 
>> this before other work intervened.
>>
>> -- 
>> John Lane Schultz
>> Spread Concepts LLC
>> Phn: 443 838 2200
>>
>>
>>
>> _______________________________________________
>> Spread-users mailing list
>> Spread-users at lists.spread.org
>> http://lists.spread.org/mailman/listinfo/spread-users
> 
> 
> _________________________________________________________________
> 
>> From must-see cities to the best beaches, plan a getaway with the Spring 
> 
> Travel Guide! http://special.msn.com/local/springtravel.armx
> 
> 
> _______________________________________________
> 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