Marty wrote:
Again, I think you are searching in the wrong direction. Your 'hdparm
-tT' results clearly showed that the great difference between your
servers doesn't lie in hard disk performance (48 to 43 MB/s), but in
Memory/CPU performance (278 to 58 MB/s).
That would be a very gross misconfiguration. To me it seems far more
likely that raid caching is simply disabled, possibly in the driver.
(Grasping straws here, but maybe the card was blacklisted for not obeying
the fsync() function, and therefore deemed unsafe for atomic commits
whenever write caching is enabled, just as one possible reason, however
unlikely. See Slashdot discussion on "Your hard drive lies to you":
http://hardware.slashdot.org/article.pl?sid=05/05/13/0529252&tid=198&tid=128
)
When doing the same SQL query
several times the hard disk shouldn't be bothered much anyway since
either MySQL or a´t least Linux itself should have cached the data.
One thing that might effect the issue, if this leads to any more
insights: The sarge box WAS a woody box.. the RAID disks were moved
between the OS versions. The woody was running RAID tools with this config:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 4
persistent-superblock 1
device /dev/hde1
raid-disk 0
device /dev/hdg1
raid-disk 1
However, the sarge box in running mdadm with this config:
DEVICE /dev/hde1 /dev/hdg1
ARRAY /dev/md0 level=1 num-devices=2 devices=/dev/hde1,/dev/hdg1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]