[Spread-users] spread multi-threaded

[Jonathan Stanton]

On Wed, Sep 10, 2003 at 01:09:34PM -0500, John Jolet wrote:
> I'm setting up a spread-based central logging server system and i've
got some logs that are incredibly high-activity.  on the central server,
i end up with what looks like the spread daemon taking up 99% of one
cpu, and none of the other.  can spread be made multi-threaded to deal
with a high volume of messages? the eventual architecture will be three
spread servers, with hundreds of clients.  the clients will not be
running spread, but will attach to a virtual ip (shared via whackamole)
between the spread servers for availability.  right now, there's just a
single spread server, so he's not having to forward the messages, and
there's no token-passing issues, since he's the only server.

It would be very difficult to multi-thread the Spread daemon. However,
it does use a very efficient event system so it can handle a large
number of connections and messages per second. Can you give us an idea
about the absolute numbers are with your "high-activity" that causes the
daemon to max out a cpu?

For example, if you can run the "spmonitor" program and copy the output
screens once you activate status reports for the daemon you are running.
That will show how many messages per second are being sent, how busy the
daemon is with other work, etc. 

Jonathan

-- 
-------------------------------------------------------
Jonathan R. Stanton         jonathan at cs.jhu.edu
Dept. of Computer Science   
Johns Hopkins University    
-------------------------------------------------------