testing Perc 6 RAID Speeds do these look ok?

AMD_Gamer

Fully [H]
Joined
Jan 20, 2002
Messages
18,287
I finally got around to installing Server 2008 R2 Enterprise on my whitebox to play around with my perc 6.

Not sure if these benchmarks look good or not. CrystalDiskMark looks good but for some reason HDtune does not report the same speeds. Also it tells me that writing is disabled so I can't run the write test.

Specs

Dell Perc 6
Windows Server 2008R2 Enterprise
4X Western Digital RE3 500GB WD5002ABYS
Raid 0 default settings
Raid 5 default settings

RAID 0:
jkimr.jpg


yzNVJ.jpg


RAID 5:

Z2YvX.jpg


Fmw63.jpg
 
It's not very good. is the array done initializing?

I did the quick initialization, is that ok?

Don't the CrystalDiskMark scores look good? It is just HDtune that is not good looking? When I do the file benchmark you can see the read/write jumping up to the speeds shown in CrystalDiskMark.
 
HD tune numbers are bad on both raid 0 and raid5 but this is probably caused by the quick initialization.
 
HD tune numbers are bad on both raid 0 and raid5 but this is probably caused by the quick initialization.

Can you explain this to me, what exactly does the initialization do? you should always do the full and not fast? what is the difference?
 
Ok I think I figured it out, HDtune is set to use 64kb blocks by default on the normal read/write tests. That means it will only be writing to a single drive if your default RAID setup uses 64kb blocks. So I changed the HDtune test block to 8MB and now everything seems to be much better.

How does this look for RAID 0 and RAID 5?

block settings:

CnBsY.jpg


RAID 5:

B7FtW.jpg


RAID 0:
GB2BP.jpg
 
Can you explain this to me, what exactly does the initialization do? you should always do the full and not fast? what is the difference?

Normally on linux software raid, windows software raid or 3ware hardware raid from 2007 when you initialize a raid 5 or 6 array that parity needs to be calculated for every stripe at the time of the initialization. This process will take as long as a rebuild takes (usually 2 hours to 1 day) where the drives would be thrashing in the background updating the parity. I have no experience with a perc or any recent HW raid but in theory a quick initialization could only initialize (calculate parity) the blocks that are in use and update as writes happen.
 
Last edited:
It includes a badblocks-check if I'm not mistaken.

Yes when the parity is calculated/updated if any sector is bad the raid will take some action depending on the raid. Some raids will kick out the drive with a bad sector.
 
HDTune tests with single queue depth; so it should not be used on RAID arrays or write-back. AS SSD and CrystalDiskMark is what you should look at. Your scores look fine to me.
 
HDTune tests with single queue depth; so it should not be used on RAID arrays or write-back. AS SSD and CrystalDiskMark is what you should look at. Your scores look fine to me.

what are the best benchmark programs for RAID? it seems everyone uses HDtune?
 
Back
Top