How many users can a WildFire server host?

General Discussion
1

I apologize for two postings that both ask “how long is a piece of string?”

In 1999 Dan Kegel wrote his inflential web page that stated that the standard of the art in distributed systems was 10,000 concurrent users per system http://www.kegel.com/c10k.html. We all know that benchmark results are nonsensical. Against that backdrop I “know” that Sonic JMS supports 13,500 messages per second - because thatwhat my host can do with my workload.

How many concurrent users does a single Wildfire servers support, if all unspecified variables have values that are reasonable to you?

2

We know of implementations with 7K concurrent users on a production box. We expect we can get more users onto a single server once we have the implementation of NIO complete (NIO is a newer IO framework in Java that’'s more scalable).

Regards,

Matt

3

Hi,

there is one guy which can not handle more than 500 users on Windows / LDAP. It’‘s not clear what’'s his problem as 1000 users should be possible without any problem.

Lg

4

Hi,

I’'m wiritng this from a non coder, non jive perspective… but from what I can see on our server (thats not busy btw) then I think it depends on what your using it for (probably not helpful so far!)…

I’'ve got it running on a pedestrian celeron 2ghz, 1gb ram and using Oracle XE for the database.

Theres a couple of things I’'ve noticed :

a) most of the processing time is when users logon / logoff

b) sending messages / file transfer is basically n/a.

Trying to pin down the basics of my config that are relevent…

We don’‘t have any logging on there, I know you can in the enterprise version, so that may slow things down a bit on the message front, and theres only 2 conference rooms (static and users can’'t create there own).

Also, remote creation of users is disabled and comms is via SSL only. Not sure if they would make any diff, I presume that SSL encryption would slow it down if anything.

As a stab in the dark, from what I’'ve seen my server could probably cope with simulatnious logons from 10 people before anyone noticed a speed change (i.e. they would all be completed in <1 sec).

For comms then as above, don’'t even see a blip on the CPU, but this may (would I think) change if theres a lot of larger conference rooms on the go as the server would be sending messages all over the place.

With regards to bandwith I really don’'t know, the servers sitting on a 100Mb internet connection so any traffic is not noticed, although we do (usually) end up falling back to transfer via the server for files as everyone is firewalled individually, so if theres a lot of files flying around then I presume bandwidth and also CPU would again go up (due to SSL and compression being enabled).

I know thats been rather rambly, but I would expect to be able to scale to tens of thousands of users provided there not all wanting to logon simultaniously without seeing a collapse in performance, provided conferencing is kept to a minimum (i.e. limit to a low number the number of users in any one room).

rambles end!

Cheers

I.