Loading...
 
Features / Usability

Features / Usability


Capacity test of the wiki 3.1 coming weekend

posts: 60

I am busy to organize a capacity test for the wiki 3.1 this coming weekend. I will ask about 2,000 (preferable more) people to get online on a certain time, so I can see how far the wiki (and my sites) can perform with more then 2,000 concurrent users.

If you guys are interested, I can give you the details (URL and time) about the capacity test and join the fun.


I had another test running last week, where I asked people trying to hack into a security site, also wiki, but version 3.0. The site is located at http://wiki.globalappsecurity.net
The wiki held itself perfectly and was able to continue running, what ever the 'hackers' were trying to do.
The only thing what they were able to do was to use cursing words as user names.

Wim


posts: 60

Alright!
The performance test will be held at:
url: http://www.writingcenter4.info
Time: Friday, 3rd of July, 8pm GMT
Number of participants: 2,600 invitees, maybe more.
Duration: Until the whole thing crashes or everyone gets enough
Purpose: To see what the performance is of TikiWiki 3.1 under a load of at least 2,000 concurrent users, preferable more.

I will release the restrictions of the site for the erotic art galleries (images and stories) as bonus for everyone during that test for a period of 24 hours.

When you guys read this, please invite everyone you know if your are interested in stress testing the wiki.

Wim
P.S. I will repeat this test again, but with full content (about 500,000 pages) and see what it does then.


posts: 60

Guys,

I've already learned one thing. When you have RSS enabled, make it as small as possible or better disable it, especially for file galleries.


posts: 60

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)


posts: 60

The conclusion is here:
http://www.hpfanficarchive.com/index.php


-

The site got visited by many people, there was a record number of people who were downloading, until the number reached of 1,502 concurrent users. Only then the engine (TikiWiki 3.1) security kicked in and refused to serve the next user. (then everyone saw the message that the server was too busy).

With this information I know that the TikiWiki is excellent and perfectly up for the job, but not for shared hosting (that is what I have at the moment for the Writing Center IV).

  • Thanks to the performance test, I continue working with the TikiWiki, because I see that it is able to handle the pressure. Because of the complixity of the software, it demands good hardware.
  • Thanks to the two teenagers, I am aware of the danger of shared hosting and want to avoid that.
  • The shared hosting account is not one of the best to have. It is regularly out of the air for minutes to hours every week. The problem what I have with the shared hosting is that it is out of my hands.


To avoid allthe problems, I hired myself a dedicated server at Rachmounted.com for $35/month. That means that I move the whole WC4 over to that new computer at the end of the coming week and the WC4 will be the only major site on that computer.

And that will conclude the new WC4, its final resting place and the place to stay.

Again, thank you so much for your help and there will be much more to come.

Wim


posts: 60

Well, I learned a lot thanks to that test.

  1. Never use the TikiWiki with a hosted provider, unless you want to take the risk that they overload the server and you will be locked out and/or suspended
  2. When you have a dedicated server, take care that you have enough memory
    1. And that is not all! You need to change the value in the php.ini (into something like

memory_limit = 700M
or more

I repeated the test before and I came up with 1,308 concurrent users and the server processor was busy average with 26% and the memory load was about 600Mb average. One thing was that my database was not big, but it had a lot of download content (files and images).


Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting