Short-Stroking hard drives

Associate
Joined
19 Aug 2007
Posts
122
Hi,
i was wondering if anyone had actually done this before? i was looking to do this in a raid 0 of 4 Spinpoint F1 1TB disks to compare to SSD and didnt know if anyone had tried any experience.

Regards Sam
 
Throughput wise that should be faster than any SSD, but the access time will be high (sum of the access time for all drives IIRK).

Also unless you have a UEFI BIOS, then you cannot boot from a partition > 2TB, so you would need to partition your RAID array into smaller partitions.
 
i think that in raid 0 the access time will be the access time of 1 drive rather than sum, as they are being short-stroked this would be less than the standard access time as it is only use part of the drive and not all of it, which would also not limit the 2tb thing as you would only be using about 250gb of each drive giving 1tb of space, also i would be using these on a sas raid card so wouldnt be a problem of 2tb.

Regards Sam
 
i think that in raid 0 the access time will be the access time of 1 drive rather than sum, as they are being short-stroked this would be less than the standard access time as it is only use part of the drive and not all of it, which would also not limit the 2tb thing as you would only be using about 250gb of each drive giving 1tb of space, also i would be using these on a sas raid card so wouldnt be a problem of 2tb.

Regards Sam

wrong in a raid array the more drives, the more access time although I don't think it's the sum of all of the drives. Here is a pretty good article about stopping the raid0 insanity:D

http://tweakers.net/reviews/515

There is no physical way any hdd setup can compare to an ssd because all the hype about the ssd is the <1ms access times. It's not all about throughput although the ssd's do have that too, but if you read the article above, you'll see that the high throughput has very little real world usage.
 
Last edited:
i think that in raid 0 the access time will be the access time of 1 drive rather than sum, as they are being short-stroked this would be less than the standard access time as it is only use part of the drive and not all of it, which would also not limit the 2tb thing as you would only be using about 250gb of each drive giving 1tb of space, also i would be using these on a sas raid card so wouldnt be a problem of 2tb.

Regards Sam

I've never heard of "short-stoking" so I couldn't comment on that, but using a sas raid card will not allow you to boot from partition >2TB unless the motherboard has a Uefi BIOS. The sas card would present the partition as a boot partition, and the BIOS would simply claim that no boot partition had been found. Apple Macs use Uefi BIOS FWIW, but 98% of PCs don't, yet. You can use partitions larger than 2TB as storage partitions, but not a boot partition.

EDIT:
OK I think I understand what short stroking is, this article might be of help if you haven't already read it...
http://www.tomshardware.com/reviews/short-stroking-hdd,2157.html
 
Last edited:
Short-stroking... I read about this a while ago. I still don't see the point when you could get the same effect just by creating a small OS partition at the start of the drive, without losing most of your disk space.
 
Short-stroking... I read about this a while ago. I still don't see the point when you could get the same effect just by creating a small OS partition at the start of the drive, without losing most of your disk space.

Enterprise usage is the only time it might be worth considering - obviously for home users, the extra capacity can be used for storage, but suppose your boot partition needed to be maybe 200GB in size, and you wanted the best possible performance, you might consider splitting it over the fastest part of four 1TB drives or something. At that point, if you don't have enough media etc to store on the remainder of those TB drives, you are effectively short-stroking.

Obviously you'd just go SSD if it were that important though.
 
Last edited:
Short-stroking... I read about this a while ago. I still don't see the point when you could get the same effect just by creating a small OS partition at the start of the drive, without losing most of your disk space.

Sort of defeats the object of doing it though. The whole point is to try and stop the heads moving out of the high performance zone at the outside of the platter. If you then go and store data on the inside of the drive the heads have to go there to get it and the access times go up/read rates go down.
 
Doesn't seem to be worth doing really...

I just had a play and heres a Seagate 500Gig 7200.12 without short stroking:

hdtune.jpg


and here is the short stroked version:

hdtune4.jpg


Even at 32gig the access times aren't even halved.

If it had even got them down to 2-3ms I'd have considered it maybe more worthwhile - or maybe if you were doing something that needed a guaranteed minimum drive speed.
 
~20% increase in average IO and 45% reduction in access time ave,

your really hard to please if that not good enough

nice charts though
 
Back
Top Bottom