On 6/11/05, tthompson(a)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