[JDEV] Jabber 1.4.2 capabilities and limitations

[Thomas Muldowney]

A few notes:

#1)  Windows is in no way our primary target.  I just did that build as
a way for people to play with everything and try it out.

#2)  There are known problems with the cygwin build and therefore is a
horrid judge of the real system.

#3)  It's cygwin, not a native build, kind of an unfair test.

--temas


On Mon, 2002-04-29 at 08:50, Lars.Nilsson4 at sas.no wrote:
> Hi. 
> 
> I'm running the 1.4.2 server on windows/cygwin.
> 
> I'm trying to run a stress test of server. I have turned of Karma (inc/dedc
> = 0) and <rate Points is set to 100, time=1. 
> 
> I have also made a server side component to offload the JSM. All messages
> are sent direclty to the server side component. 
> 
> The clients are very simple: connect and send a message on a spesified
> timer. 
> 
> The test where done several times and the same occured every time!
> 
> 1) Test one:
> One message pr second:
> 	When i reach 45-50 clients jabber jumps from <10% CPU time to >95%
> !!! 
> 
> 2) Test two:
>  I keep the number low <45 -> jabber cpu <10%.
>  I go slowly down to one message pr 50 millisecond. After some 2-3 minuttes
> jabberd crashes!!!
>  
> I though jabber was supposed to handle loads of clients (read thousands;
> even with the limitiation of cygwin). And not certainly not eat all
> resources at only some 40-50 clients.
> 
> If any one wants to test this, i can send them all components in the test
> scenario.
> 
> Are these limitations wel-know or is it bugs?
> 
> regards,
> lars.
> 
> 
> 
>  
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev