We're using MediaWiki on our corporate Intranet with great results. It's perfect even for a smaller company.
The configuration is as follows: MediaWiki (http://wikipedia.sf.net/): 1.4.4 PHP (http://www.php.net/): 4.3.10 (apache2handler) MySQL (http://www.mysql.com/): 4.0.18-max-debug-log IIS 5.x Windows 2000 Server on 2Ghz Pentium 4, 512MB RAM, SCSI RAID array Also: Apache 2.0.52 for testing
This rather non-trivial server gets a 100% CPU spike for 2 to 5 seconds on each page view in the wiki. Ugh!
Apache on that same server didn't give any noticable speed improvements.
Just on a whim, I installed the same MediaWiki code on a Linux laptop, running PHP 4.3.10 and the same Apache version. It's querying the MySQL database on the main server.
The Linux/PHP/Apache on the Pentium 3 850Mhz laptop with half the RAM is nearly FOUR times faster! That's half the RAM, a third the CPU speed... but it dusts Windows 2000.
I can bring up two browser windows, with the Windows wiki in one and the Linux wiki in the other, and click "Random page" in both windows. I can click thru 4 or 5 random pages in the Linux instance in the time the Windows instance brings back one.
To get Windows performance like that, I had to run the PHP code on a dual CPU P4 with 1GB RAM under Windows 2003 Server.
Are there any optimization options I could be missing? I've already enabled page caching on the server (works well), installed the Zend Optimizer (free version), and ensured that I'm not dealing with the dreaded multi-redirect bug. The CPU hit on the Windows server is huge. MySQL isn't breaking a sweat at all.
On 6/11/05, tthompson@envisionware.com wrote:
... MySQL (http://www.mysql.com/): 4.0.18-max-debug-log ... MySQL isn't breaking a sweat at all.
Are you sure? My first guess would have been MySQL. See http://dev.mysql.com/doc/mysql/en/windows-select-server.html
Which process is using the CPU? (or is it System?)
It may also be worth checking any real-time anti-virus settings.
-- Zigger
On 6/11/05, tthompson@envisionware.com wrote:
... MySQL (http://www.mysql.com/): 4.0.18-max-debug-log ... MySQL isn't breaking a sweat at all.
Are you sure? My first guess would have been MySQL. See http://dev.mysql.com/doc/mysql/en/windows-select-server.html
Good idea. I'll switch MySQL versions to something a bit less weighty.
Which process is using the CPU? (or is it System?)
The inetinfo.exe process jumps to 50-98% for several seconds on each wiki page.
It may also be worth checking any real-time anti-virus settings.
Thanks for the idea. I disabled it temporarily (Symantec AntiVirus 9.0 Corporate Edition) but there was no noticeable change.
All leads point to the web service or PHP as the culprit... so far. During wiki page generation, the inetinfo.exe process allocates and releases about 8MB of memory, so it's apparently doing something substantial.
It would be nice if it did it faster, though. Comments have been made around the company about the wiki performance being a bit lackluster. *sigh*
Any other paths to try? I've attempted the page generation timing statistics thingy in Mediawiki, but I don't think I enabled enough detail. I get HTML comments in the pages for my personal ID with a summary.
On the Windows 2000 / IIS server, I get:
- Served by intrawiki.envisionware.com in 1.22 secs.
On the Linux Fedora Core 2 / Apache laptop, I get:
- Served by ntop-internal.envisionware.com in 0.35 secs.
The Mediawiki code just seems MUCH slower on Windows 2000. Maybe LAMP (Linux/Apache/MySQL/PHP) is the way to go, and WIMP (Windows/IIS/MySQL/PHP) is not just an acronym? *wrysmile!*
- Troy Thompson
I have a similar problem with the Wiki I run, it is running on Windows and IIS with MySQL and PHP. Whenever you click a link CPU usage jumps to about 50-70% for about a second or two, I carefully watched the processes and the main usage comes from the php process, this starts running uses a lot of processor power and then closes.
There are several bugs listed with php.net about slow windows performance but no fixes that I can find.
I have had other more important problems with my wiki recently so I haven't spend much time on this one.
Arthur Guy
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of tthompson@envisionware.com Sent: 12 June 2005 05:41 To: Zigger; MediaWiki announcements and site admin list Cc: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Windows Apache & IIS vs Linux Apache performance differences
On 6/11/05, tthompson@envisionware.com wrote:
... MySQL (http://www.mysql.com/): 4.0.18-max-debug-log ... MySQL isn't breaking a sweat at all.
Are you sure? My first guess would have been MySQL. See http://dev.mysql.com/doc/mysql/en/windows-select-server.html
Good idea. I'll switch MySQL versions to something a bit less weighty.
Which process is using the CPU? (or is it System?)
The inetinfo.exe process jumps to 50-98% for several seconds on each wiki page.
It may also be worth checking any real-time anti-virus settings.
Thanks for the idea. I disabled it temporarily (Symantec AntiVirus 9.0 Corporate Edition) but there was no noticeable change.
All leads point to the web service or PHP as the culprit... so far. During wiki page generation, the inetinfo.exe process allocates and releases about 8MB of memory, so it's apparently doing something substantial.
It would be nice if it did it faster, though. Comments have been made around the company about the wiki performance being a bit lackluster. *sigh*
Any other paths to try? I've attempted the page generation timing statistics thingy in Mediawiki, but I don't think I enabled enough detail.. I get HTML comments in the pages for my personal ID with a summary.
On the Windows 2000 / IIS server, I get:
- Served by intrawiki.envisionware.com in 1.22 secs.
On the Linux Fedora Core 2 / Apache laptop, I get:
- Served by ntop-internal.envisionware.com in 0.35 secs.
The Mediawiki code just seems MUCH slower on Windows 2000. Maybe LAMP (Linux/Apache/MySQL/PHP) is the way to go, and WIMP (Windows/IIS/MySQL/PHP) is not just an acronym? *wrysmile!*
- Troy Thompson
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
Question: is this comparison between LAMP vs WIMP implementations of the same software being made on molecularly identical hardware? The LAMP configuration is about 3 1/2 times faster than the WIMP configuration.
On 6/12/05, tthompson@envisionware.com tthompson@envisionware.com wrote:
On 6/11/05, tthompson@envisionware.com wrote:
... MySQL (http://www.mysql.com/): 4.0.18-max-debug-log ... MySQL isn't breaking a sweat at all.
Are you sure? My first guess would have been MySQL. See http://dev.mysql.com/doc/mysql/en/windows-select-server.html
Good idea. I'll switch MySQL versions to something a bit less weighty.
Which process is using the CPU? (or is it System?)
The inetinfo.exe process jumps to 50-98% for several seconds on each wiki page.
It may also be worth checking any real-time anti-virus settings.
Thanks for the idea. I disabled it temporarily (Symantec AntiVirus 9.0 Corporate Edition) but there was no noticeable change.
All leads point to the web service or PHP as the culprit... so far. During wiki page generation, the inetinfo.exe process allocates and releases about 8MB of memory, so it's apparently doing something substantial.
It would be nice if it did it faster, though. Comments have been made around the company about the wiki performance being a bit lackluster. *sigh*
Any other paths to try? I've attempted the page generation timing statistics thingy in Mediawiki, but I don't think I enabled enough detail. I get HTML comments in the pages for my personal ID with a summary.
On the Windows 2000 / IIS server, I get:
- Served by intrawiki.envisionware.com http://intrawiki.envisionware.comin
1.22 secs.
On the Linux Fedora Core 2 / Apache laptop, I get:
- Served by ntop-internal.envisionware.comhttp://ntop-internal.envisionware.comin
0.35 secs.
The Mediawiki code just seems MUCH slower on Windows 2000. Maybe LAMP (Linux/Apache/MySQL/PHP) is the way to go, and WIMP (Windows/IIS/MySQL/PHP) is not just an acronym? *wrysmile!*
- Troy Thompson
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org]On Behalf Of FL Sent: Sunday, June 12, 2005 3:02 PM To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Windows Apache & IIS vs Linux Apache performancedifferences
Question: is this comparison between LAMP vs WIMP implementations of the same software being made on molecularly identical hardware? The LAMP configuration is about 3 1/2 times faster than the WIMP configuration.
The comparison is on vastly different hardware. The LAMP hardware is a Pentium 3 laptop at 850Mhz, 200MB RAM. The WIMP hardware is a Pentium 4 server at 2+ Ghz, 512MB RAM.
This actually makes the speed of the LAMP implementation even more stunning; at half the CPU and half the RAM, it's consistently 4 times faster than the WIMP server.
- Troy Thompson
Can I get some feedback from people as to the average page load time (as shown in the comment at the bottom of each page).
I have been running MediaWiki on IIS on windows and I have been getting average times of 0.5s I then installed apache on my laptop and setup MediaWiki to get data from the original database, with this setup I am getting 0.4s. The laptop isn't as good as the server and it was getting its data across the network so it shows how much better Apache is with this type of site.
What I would like to know is 0.5s or 0.4s fast or slow, what times are other people getting, and what are they running, WIMP, WAMP, LAMP, etc...
Thanks Arthur
arthur@astarsolutions.co.uk www.astarsolutions.co.uk
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of tthompson@envisionware.com Sent: 11 June 2005 05:21 To: mediawiki-l@Wikimedia.org Subject: [Mediawiki-l] Windows Apache & IIS vs Linux Apache performancedifferences
We're using MediaWiki on our corporate Intranet with great results. It's perfect even for a smaller company.
The configuration is as follows: MediaWiki (http://wikipedia.sf.net/): 1.4.4 PHP (http://www.php.net/): 4.3.10 (apache2handler) MySQL (http://www.mysql.com/): 4.0.18-max-debug-log IIS 5.x Windows 2000 Server on 2Ghz Pentium 4, 512MB RAM, SCSI RAID array Also: Apache 2.0.52 for testing
This rather non-trivial server gets a 100% CPU spike for 2 to 5 seconds on each page view in the wiki. Ugh!
Apache on that same server didn't give any noticable speed improvements.
Just on a whim, I installed the same MediaWiki code on a Linux laptop, running PHP 4.3.10 and the same Apache version. It's querying the MySQL database on the main server.
The Linux/PHP/Apache on the Pentium 3 850Mhz laptop with half the RAM is nearly FOUR times faster! That's half the RAM, a third the CPU speed... but it dusts Windows 2000.
I can bring up two browser windows, with the Windows wiki in one and the Linux wiki in the other, and click "Random page" in both windows. I can click thru 4 or 5 random pages in the Linux instance in the time the Windows instance brings back one.
To get Windows performance like that, I had to run the PHP code on a dual CPU P4 with 1GB RAM under Windows 2003 Server.
Are there any optimization options I could be missing? I've already enabled page caching on the server (works well), installed the Zend Optimizer (free version), and ensured that I'm not dealing with the dreaded multi-redirect bug. The CPU hit on the Windows server is huge. MySQL isn't breaking a sweat at all.
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
'a star solutions' disclaimer The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Any views expressed in this message are those of the individual sender and may not necessarily reflect the views of the company. We believe that this communication is free from viruses and other potentially dangerous programmes, but the recipient opens this communication at their own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this communication
Arthur Guy wrote:
Can I get some feedback from people as to the average page load time (as shown in the comment at the bottom of each page).
I have been running MediaWiki on IIS on windows and I have been getting average times of 0.5s I then installed apache on my laptop and setup MediaWiki to get data from the original database, with this setup I am getting 0.4s. The laptop isn't as good as the server and it was getting its data across the network so it shows how much better Apache is with this type of site.
What I would like to know is 0.5s or 0.4s fast or slow, what times are other people getting, and what are they running, WIMP, WAMP, LAMP, etc...
My test box at home is a 2GHz Athlon XP w/ 512 MB ram, running Ubuntu Linux (Hoary Hedgehog). Apache 2, PHP 4.3.10, MySQL 4.0.something versions shipped with Ubuntu. Figures here are given with MediaWiki 1.4 current from REL1_4 branch in CVS.
Times are measured by loading a page in Safari on another machine on the local network and reloading, then checking the comment in view source. Note that due to HTTP caching, in many browsers hitting the 'reload' button by itself will give you the exact same page back with a 304 Not Modified response; try shift+reload or ctrl+reload or cmd+reload to force a new page load.
Times will be generally be slightly slower if you load from a browser running on the server. Discard the first hit, which may be filling caches and loading code for the first time.
With Turck MMCache installed to avoid redundant compilation of PHP scripts, a page load that makes use of the parser cache (previously rendered page) or is very very short ;) takes about 0.04-0.06 seconds on this machine.
Without Turck MMCache, all the scripts have to be parsed and compiled on every hit which slows things down; it runs more about 0.14-0.17 seconds.
If you're not using Turck MMCache or the newer version EAccelerator (Turck is no longer maintained; EAccelerator is a fork of it) you really probably ought to. Note: do not turn on the experimental use of Turck's internal caching functions for MediaWiki's data cache -- that will generally fail and make things worse. Just install it and let it cache compiled PHP.
Performance for 1.4 and 1.5 should be roughly similar; 1.3 was a bit slower (and doesn't use the parser cache by default).
If you're having performance problems you should also try enabling the internal profiler ($wgDebugLogFile and $wgProfiling) to see if you can isolate something.
-- brion vibber (brion @ pobox.com)
mediawiki-l@lists.wikimedia.org