From: Joyce P. <tru...@ya...> - 2003-12-15 18:39:16
|
Hi Robert! So I would not personally use the Perl server in a production environment. It's really meant for light use in shared hosting situations. In terms of bandwidth -- that's never been the limiting factor. CPU becomes an issue if you have a lot of events and especially a lot of clients because of the inefficient nature of our expired event reaping. Mod-pubsub can be made to work in situations where lots of events flow through to very few clients. Here's a writeup someone did about a commercial product with an embedded Mod-pubsub system in that situation: http://www.mod-pubsub.org/moinmoin/PythonServerWithOnePerlClientAndManyEvents But it starts to have problems in situations where there are many clients, each of which connects and only consumes a few events. Also, we lack important scalability features like failover and replication due to some constraints imposed by KnowNow on some of our developers. If you work up some performance numbers, we'd love to see them, Joyce Park --- Robert <es...@ya...> wrote: > > I'm an independent consultant being asked to evaluate the mod-pubsub > software for a client. I was hoping someone could give me info on > which implementation to try first, the perl module or python server? > > Also, for each implementation, are there any stress testing results > available to give me an idea on the sort of bandwith and cpu > requirements there should be for a given # of topic updates per second > and/or active subscription count? > Thanks in advance, > Robert Sweeney |