Hard Drive chunk size?

  • Thread starter Thread starter Rush
  • Start date Start date
R

Rush

I just installed on my 7n8x two WD Raptors SATA drive in raid 0. The raid
bios setup wanted to know what chunk size to set. 16k was default but there
were many to choose from. The manual did not cover this. I sure don't want
to reload windows unless there is a huge performance gain in increasing this
value
 
Most suggestions I've seen range drom 64-128K in size. Some go as high as
256, but you see a diminishing return there. Some controllers offer a max of
64K.
 
Rush:


I can't shed any light on the proper chunk setting, but I sure would be
curious about what kind of SiSoft (file system benchmark) score you get with
a pair of Raptors in Raid 0.

I am running a single Raptor on the same motherboard with SiSoft benchmark
of 36,000 kB/s, which is a 20% improvement over my WD1200JB drive at 30,000
kB/s.
 
From what I have read on this matter, it all depends on what you are intending
to use your RAID array for. If you plan on doing most large file size transfers
such as with audio/video, then you should make the chunk size large. If you
plan on doing mostly small file size transfers such as maybe with a web server,
then use a small chunk size. If you plan on doing a mixture of both large and
small file size transfers, then choose something in the middle.

From what I recall reading, a RAID controller transfers complete blocks of data
to or from the RAID set (commonly called chunks). If you make your chunk size
large, oh say like 256KB, and you only transfer a 5KB file the whole chunk most
still be read from and written to the array. This would waste time because the
RAID controller must first retrieve the data and then write it back to the
array. The opposite end of the spectrum would also make you loose some time if
you made your chunk size 16KB and you needed to write a 200MB .avi file to the
drive since the RAID controller would need to access 16x as many blocks than if
you set it up for 256KB chunk size.

The chunk size is not to be confused with cluster size since that is what the
file system looks at as the smallest block to transfer. I try and use this as my
rule-of-thumb:
Mostly small files=16KB to 32KB chunk size
Mixture of large and small=32KB to 64KB chunk size
Mostly large files=64KB to 128KB chunk size (256KB if the controller supports
it--mine doesn't)

Paul
 
Great explanation Paul, but if I'm not mistaken the desirable cluster size
should match the chunk size for max efficiency, e.g cpu utilization, avg
access rate etc...

JR
 
Back
Top