Re: Capacity test of the wiki 3.1 coming weekend
Another important thing I've learned.
When you use TikiWiki with a shared hosting account, that might get dangerous. The TikiWiki version 2.x was very heavy and when it contains a lot of pages, slow. When there are many users concurrent online, it brings up the processor easily to 60-90% (32Mb RAM, single processor).
With the latest version (TikiWiki 3.1), 128Mb RAM, 4 processors, easily 40%-60%!
In reality, when you have a shared hosting account, you agree mostly with the rules (when you sign up) that you must not overload the server; you are allowed peaks up to 10% of the server processor.
That means if you run the TikiWiki in a shared hosting environment, it will get your account suspended or even canceled.
There is a good thing with the TikiWiki.
When the threshold of the server is above the entered value (i.e. 3), it will close the site and displays a message. That works fine and it might protect you against suspension.
The best thing what you can do is using the TikiWiki with a dedicated server, so you have no problems like that.
I know it is expensive, more expensive then hosting, but there are dedicated servers out there, which are payable.
I ordered this afternoon a dedicated server when I saw the problems coming.
It's indeed cheap (about $35/month) at www.rackmounted.com
Anyhow, I counted the number of users active and I came up with more then 1,000 online users before problems started to appear (128Mb, 4 cpus)