[JDEV] Sparse considerations about server status

[Dustin Puryear]

On 29 Jul 2001 23:19:30 +0200, Gian Filippo Pinzari wrote:
> > Notice that at >= 120 user pairs (240 connected users), which equates to 
> > 120 msg/sec in this test, my message loss rate varies from 3% to 13%. 
> > The average delivery also climbs to .14 seconds, but I don't consider 
> > that a problem. (However, the worst case delivery times are bad: > 6 
> > seconds for 150 and 160 user pairs.)
> We've just developed a project (client+server) for one of the 
> biggest ISP in Italy. We found since the beginning that each 
> Jabber server was not able to handle more than a couple hundreds 
> client, so we implemented an architecture that load balances the 
> traffic among many concurrent servers running on the same or 
> different hosts. We also encountered message losses, but we didn't 
> care much :-). As Dustin, we thought this was due to client 
> problems.

Well, now that I know someone else has had a similar experience I can
only assume the problem is with jabberd. I had hoped that jabber.org
would confirm this to either be a problem or something they had built
into jabberd, but that information hasn't been very forthcoming.

In the end I suppose developers using jabberd need to realize that it
only works in low to medium load environments where message delivery is
not a big issue. Unfortunately, I am not sure if the same is true of the
jabber.com server since they didn't present any information on this
topic either.

Regards, Dustin

--
Dustin Puryear <dpuryear at usa.net>
http://members.telocity.com/~dpuryear
In the beginning the Universe was created. 
This has been widely regarded as a bad move. - Douglas Adams