RAID-0 and partition location

The Borg

Senior member
Apr 9, 2006
494
0
0
Hi all,

I read an article a little while back trying to see if a RAID setup could manage to reach the speed of SSD's in a price comparison way. SSD's are very expensive, but fast, so the idea was to buy lots of HDD's and RAID them, then only use the outer portion of the drive as the RAID array. In effect only using say 5% - 10% of the array to make an equivalent drive to the SSD, but even with lots of HDD's, it would still be cheaper than the SSD. It came close.

Anyway, I tried this idea on a friends HDD (single drive) by using partitoning software to make the boot drive the outer part of the drive (the faster part). I got it right, but as I don't have access to the machine, I cannot confirm performance to prove I got the right end of the drive.

The point is that the idea should work, I just want to confirm the poistion before I do this on a RAID-0 setup I want to do on my own drives.

The question is: If I get partitoning software like Partition Magic to create the boot drive at the "end" of the drive, is this infact the outer edge which is then the faster part?

If so, I can kick myself for not having done this years back as I have almost by default split drives to create a Boot and Software partitions incase the OS went south. Thus, I have always had the OS on the slower partition, thinking that a small partition would actually help by reducing head search.

Anyway, any comments woudl be appreciated.
 

alcoholbob

Diamond Member
May 24, 2005
6,390
470
126
I would think one way to split it up is to make as many partitions as there are platters on your drive, then move temp directories to the other partitions. This should allow one read/write head to focus on reads, and the other on writes.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
I would think one way to split it up is to make as many partitions as there are platters on your drive, then move temp directories to the other partitions. This should allow one read/write head to focus on reads, and the other on writes.

Maybe, if you could prove that's how the partitions ended up and that was how I/O was being handled by the drive. But you can't because the firmware on the drive can reorder I/O and you can't even be sure that the information presented by the firmware is really how the drive looks on the inside.