[Spread-users] spread multi-threaded

[John Jolet]

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.