[Spread-users] Hard limits
jgreen at spreadconcepts.com
Wed May 30 10:24:19 EDT 2007
Yes, theoretically that would be the max, but the max is actually a lot
lower. We usually don't recommend running more then a few dozen daemons per
configuration. Spread uses a token ring type protocol and if the token
traversal becomes too big, the latency of the token starts approaching the
token lost timeouts. This is one example of why its not practical to scale
Spread to huge numbers of daemons.
However, I don't see why you need to. Spread can handle hundreds of clients
per daemon, and dozens of daemons. So just run client on your machines, and
a few daemons.
You can run multiple Spread configurations on different ports, but they will
not talk to each other.
From: spread-users-bounces at lists.spread.org
[mailto:spread-users-bounces at lists.spread.org] On Behalf Of Paul B. Anderson
Sent: Wednesday, May 30, 2007 7:45 AM
To: spread-users at lists.spread.org
Subject: [Spread-users] Hard limits
I'm new to spread but thinking of using it to control hundreds of blade
computers. There are some statements in the documentation about hard
limits but I'm not sure I understand them.
The documentation says "128 machines per segment and up to 20 segments
with a total of 128 machines at most in a configuration. The 128
machine limit is a hard limit...".
128 machines per segment and 20 segments seems to imply 2560 machines.
If 128 machines is the limit, can I run multiple spreads on different ports?
Spread-users mailing list
Spread-users at lists.spread.org
More information about the Spread-users