[JDEV] Performance

temas temas at box5.net
Tue Apr 25 13:36:29 CDT 2000


Just to throw some notes into this thread.  I'm currently pushing a box up to
10,000 concurrent sessions while stress testing jabber.  I don't want to reveal
info on this box until I'm done with all my testing, but I'll give a few hints.

1)  Enable higher inode and file descriptors counts on the system

    echo 32768 > /proc/sys/fs/file-max
    echo 65536 > /proc/sys/fs/inode-max
    
2)  Raise the max sockets 
    
    ulimit -n 32768

3)  Have enough ram.  Jabber currently uses 16K per conn and a linux socket is
    8K (from what I hear).

4)  Turn off the rate limits!  (I'm putting this in as a compile time option for
    RC and 1.0).

I should be back with some fun number later this week.

--temas

On Tue, Apr 25, 2000 at 10:19:43AM -0400, Michael Petras wrote:
> One aspect of performance I was wondering how Jabber addresses is the number
> of open sockets. Does the
> Jabber server keep a TCP socket open for each logged in client? What
> determines how many sockets can be open
> simulatenously using Linux? Does Jabber or Linux do any tricks to increase
> the number of open sockets (such as
> transforming open, but quiet sockets into some placeholder objects that use
> minimal memory until the next message)?
> Does anyone know of any implementations that do this? Does anyone know how
> big IM/presence servers like Yahoo, ICQ 
> or AOL handles this?
> 
> Our applications have to communicate with tens to hundreds of thousands of
> fairly low traffic clients. Our servers run on 
> Windows NT where the limit on open sockets is a significant issue. Thanks in
> advance for any info.
> 
>  
> Thnx,
>  
> Mike Petras
> 
> > -----Original Message-----
> > From:	David Waite [SMTP:mass at ufl.edu]
> > Sent:	Tuesday, April 25, 2000 8:26 AM
> > To:	jdev
> > Subject:	RE: [JDEV] Performance
> > 
> > It sounds more like the test was throttled due to you sending too many
> > messages at once, rather than any sort of scalability or other type of
> > limitation in the Jabber server.
> > 
> > -David Waite
> > 
> > 
> > -----Original Message-----
> > Hi ,
> >         The real issue which I want to highlight is not spammers but the
> > Scalability of Jabber . The tests which I performed on Jabber clearly
> > showed
> > that it slows down which is definitely not acceptable in real-life
> > situations . Jabber has to be more scalable than it is now . Any Thoughts
> > and Ideas ?
> > Regards ,
> > chetan s . ithal
> > 
> > 
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20000425/4615bada/attachment-0002.pgp>


More information about the JDev mailing list