The first limiting factor is the one you've tried to compensate for, which is that
select is limited to FD_SETSIZE. Have you recompiled the jabberd source since the
kernel tweaking? Also, another problem you might face is with the maximum number of
open file descriptors any process can have at a given time (defaulted to 1024, varies
by the OS). You can look into using ulimit to raise this threshold (ulimit -n 65536).
That being said, instead of tweaking jabberd, you should take a look at the dpsm and
jpolld daemons. They both offer ways to distribute the socket connection bottleneck.
Basically, their only purpose is to manage client connections and funnel information
to and from the main jabberd (via a single master connection to the server). The
other advantage of these is that they both use poll to manage the I/O notifications
instead of select. Poll does not suffer from the FD_SETSIZE limitation, so the
kernel tweaking isn't necessary (although, the ulimit tweak is still needed).
Anyway, I hope that helps. Your results may vary.
Jeremey Zela
Northridge Systems, Inc.
-Original Message-
From: Riyaad Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 15, 2002 9:46 AM
To: Jabber Administration (E-mail); Jabber Developers (E-mail)
Subject: [JDEV] Max number of usersrevisted!
Hi all
Small question ...
What is the limiting factor on the number of simultaneous connections to jabberd?
I'm currently using jabber 1.4.1 open source. It cries at 1000 (about) despite
tweaking mgy kernel to get beyond 6 fd's.
Are there any thread number issues involved? Could I run multiple jabberd processes on
different ports to get a higher total number of connections to my server?
Thanks
Regards RM
Give your child an unfair advantage with M-Web Learning. To join, call 08600 32 000
or go to http://join.mweb.co.za
M-Web - JUST LIKE THAT
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
