Discussion in 'Storage' started by CrAsHnBuRnXp, Nov 2, 2007.
Wait can someone explain to me Strip Size??? 64K 128K which is better?
Simplest way to explain this is:
When you create a raid array the disks are segmented into blocks, this is the minimum amount of space a file will take up:
So if you have block size of 64k and write a 2k file, the file will use up 64k of space, if you use block size of 128k the file will take up 128k
So why bother:
If you have a file which is 64000k is will take up 1000 blocks with 64k block size, and 500 with 128k blocks.
Now since each block has its own location on the disk with 128k block size the disk will seek 50% less
So in short:
Small block/stripe size = best use of space but more seeks on the disk (very good if you are storing lots and lots of very small files or are using a database application that makes lots and lost of small reads)
Large block/stripe size = more wasted space but saves on disk seeks (Very good if you are storing large files and want to minimise the effects of disk access times (seeks))
Bump for a sticky?
That would have to be the best explanation on the entire internet.
Well done IggSter
You need not worry about wasted space when choosing a stripe size. Stripe ≠ cluster.
While yes the controller works with data at these sizes, the OS does not. It's not even aware that it's on an array of any sort.
This needs to be a sticky and moved to storage
Ive been saying sticky since i first wrote this.
Separate names with a comma.