Join for quick access. Enter your email below and we'll send confirmation plus sign you up to our newsletter.
By submitting your information, you confirm you are aged 16 or over,
have read our
Privacy Policy
and agree to the
Terms & Conditions. Geographical rules apply.
Join for quick access. Enter your email below and we'll send confirmation plus sign you up to our newsletter.
By submitting your information, you confirm you are aged 16 or over,
have read our
Privacy Policy
and agree to the
Terms & Conditions. Geographical rules apply.
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
You are now subscribed
Your newsletter sign-up was successful
Join the club
Get full access to premium articles, exclusive features and a growing list of member rewards.
An account already exists for this email address, please log in.
In RAID arrays, the block size generally also determines the stripe size (not in RAID 1). The principles concerning block size and wasted memory space apply equally to RAID configurations: if, for example, the blocks have a size of 64 kB, then at least 64 kB are written at all times - even if there's only a text file with 2 kB. So, the smaller the average file size, the smaller the block size should be.
But block size is also significant in terms of the performance to be expected, as the smallest unit also determines when a file can be distributed to two or more drives. This would mean that with a block size of 64 kB, files with less than 64 kB would be written to only one hard drive. This does not happen any faster in a RAID array than on a single hard drive.
On the other hand, a file with 150 kB would be distributed to three hard drives (if available): 64 + 64 + 22 kB. The controller is now able to read from all three drives simultaneously, which reduces the read operation immensely.
Patrick Schmid was the editor-in-chief for Tom's Hardware from 2005 to 2006. He wrote numerous articles on a wide range of hardware topics, including storage, CPUs, and system builds.
