jasonslogan
asked on
Mysql slow on Windows 2008 Server
I have two mysql servers:
HP DL380 G3 4GB RAM 32bit running linux with mysql 5.0.45
and
HP DL180 G6 16GB RAM 64bit running win2008 with mysql 5.1.47
Here's the thing...
My linux box (32bit 4GB) will run X query in 15 seconds. My windows box (64bit 16GB) in 55 seconds. Also the windows box has dual quad core processors while the linux box has dual dual cores.
The windows box should be annihilating the linux box. Is there a way to tweak the windows mysql to work faster or should I switch it to linux? I did install the windows mysql 64bit version and chose during the install to use all the resources of the box. Nothing else is on this box but mysql. While the linux box is also a webserver.
HP DL380 G3 4GB RAM 32bit running linux with mysql 5.0.45
and
HP DL180 G6 16GB RAM 64bit running win2008 with mysql 5.1.47
Here's the thing...
My linux box (32bit 4GB) will run X query in 15 seconds. My windows box (64bit 16GB) in 55 seconds. Also the windows box has dual quad core processors while the linux box has dual dual cores.
The windows box should be annihilating the linux box. Is there a way to tweak the windows mysql to work faster or should I switch it to linux? I did install the windows mysql 64bit version and chose during the install to use all the resources of the box. Nothing else is on this box but mysql. While the linux box is also a webserver.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is always good to have proper backups, and nothing beats the scripting functionality of unix or linux for mysql dump, tar and gzip scripts.
Just do regular mysql dumps to a different drive to make sure you can recover from a serious crash.
http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html
I have been working with ext file systems for the last 11 years, and I have never seen anything close to what you experienced. It may not start up if it was shutdown uncleanly, and will sometimes require the root password for recovery when you boot it up afterwards. But all errors will be fixed most of the time.
If you want to read more about ext4 - http://en.wikipedia.org/wiki/Ext4
Just do regular mysql dumps to a different drive to make sure you can recover from a serious crash.
http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html
I have been working with ext file systems for the last 11 years, and I have never seen anything close to what you experienced. It may not start up if it was shutdown uncleanly, and will sometimes require the root password for recovery when you boot it up afterwards. But all errors will be fixed most of the time.
If you want to read more about ext4 - http://en.wikipedia.org/wiki/Ext4
ASKER
I had a redhat box with an ext3 fs that was writing to a root directory when the power failed. That directory became unreadable and there are limited tools to fix fs problems in linux. Window's chkdsk is great at fixing problems.