Quote:
Originally Posted by c00lkatz

Thanks for the replies. I was under the assumption that a true short-stroke was setup while setting up your actual array and reformatting. I basically have a full 1.16TB array, but I did partition, but everything is still on the RAID 0 array. In HDTune and other benchmarks, I am not getting results even close to others who have setup their array for only a small portion of disk space, losing the rest of the drive space.
I just didn't want to throw down the cash, reformat, reinstall everything, lose a full TB of drive space and not notice a nice difference.
My PC isn't slow by any means, but I know every little bit helps. I mostly just listen to music, surf the net, watch movies, and game. I don't do any encoding or anything like that.
|
The way I understand it. It works kind of like this.
The first 1/4 of your benchmark = 100% of a short-stroked benchmark.
So basically by short-stroking, you are limiting HD Tune to only bench a portion of the outer edge of the platters.
Your HDTune benches start from the outer edge, but then go past the cutoff point that someone would have short stroked too. When your bench gets past that point where someone would have short-stroked to, that's the other 3/4 of your benchmark where your speeds start to get slower.
So basically if you partition C:\\ first on your raid array (on the outer edges) and you have a well defragged drive - and your drive is only reading/writing from/to C:\\ then you will see the performance of a short stroked drive.
As soon as your drive starts reading past the first 10-25% of your drive (where most people stop on a short stroke) then that's when your graph starts to slope downwards.
Benefits - (of short stroking)
Faster access times - by limiting the area that the heads have to travel back and forth from.
Faster "On Average" Seq Read/Writes only by way of denying yourself access to slower sections of the disk
Cons -
Can only use 10-25% of your total storage space.