Just stumbled in here this evening. Glad to find a forum like this. Hope I can help as well as be helped.
Anybody ever done any serious testing of mySQL performance differences on Windows servers vs. Linux servers?
I moved a busy Invision Board forum (300MB db, 200+ active users) off of a Cobalt RAQ4 that was dying under the load. I split the web server and the database server. The new web server is a Celeron 2.4 with 1GB RAM, running Win 2003, IIS and PHP in CGI mode. The new database server is a Dual PIII 600 with 768MB RAM and SCSI drives, running Win 2000 and mySQL 4.1.7nt.
The anemic RAQ4 with it's puny AMD 400mhz processor, 512MB ram, and IDE drive, was serving about 15 other low-traffic sites in addition to the mySQL server and the busy Invision forum. It actually did a fairly credible job keeping up untl the forum got to 125 or more active users. After that, it got doggy.
The new web server and database server are doing little else except serving this forum, yet I am already maxing out at 500MB and 250 to 300 active users. The db server is tuned to use all of the RAM for MySQL (without resorting to swapping). I've tinkered with the my.cnf parameters many times. Yet, at peak periods with 250 or more active participants on the forum, both CPUs on the database server are pegged at 95% or better, and performance goes down the toilet.
I expected much better performance considering the dramatic upgrade in hardware, and I am wondering if mySQL on Windows is simply a much worse performing than on Linux.
Any suggestions, experiences in this area, anecdotal tales, spells, voodoo, or other relevant comments greatly appreciated.
Side note: Windows 2003 has proven to be a big disappointment from a web server stability standpoint. I have no axe to grind against Windows 2003; I use it in a shared hosting enviroment with great stability. I believe the problem is PHP, which doesn't seem to coexist very well.