Overclock.net banner

Samsung F3 1TB Raid 0 HDtune Result

23474 Views 31 Replies 8 Participants Last post by  SyncMaster753
Here are my results from HDTune using two Samsung F3 1TB Models set to Raid 0 @ Short-stroke 48gig using 64k Stripe.

This is my OS drive, hence the small irregularities.

Hope these are useful for someone hoping to raid these puppy up.

HDtune Random Access



HDtune Benchmark



HDtune File Benchmark 8mb



Id
See less See more
3
1 - 20 of 32 Posts
Not sure yet, might leave it blank. Not really needing the space as I got a 2nd 1TB samsung (F1) for storage.

I got two options,

a) set it up for Raid 0, and use if for games, bench app's etc

b) set it up for Raid 1 if need and use it as a backup (might be safer than the single F1)
I wonder how it would scale with 3, looking at other setup's, seems 3 or more might not be beneficial. Interesting.. Running ICHR9
Quote:

Originally Posted by IdPlease View Post
I wonder how it would scale with 3, looking at other setup's, seems 3 or more might not be beneficial. Interesting.. Running ICHR9

3 is about the max on the ichr9.
I should have went with 3, but no room.
See less See more
Im tempted to get another, just to see but having like 2.8tb free space is a lot. I'd never fill it.

Be nice if it came close, or higher then 350mb/s, doubt the seek time would change from 7ms tho.

Not 100% sure why the burst rate is so low (even if it matters). Don't think the stripe size would make much of a difference.

Only one way to find out I guess ...
Wow! I just purchased 2 F3s after having caviar blacks, Im running a ICH10R planning on running both 1tb drives in a RAID 0.

How do you know what size to short stroke the drives at? I honestly dont need more than 20 gigs for my OS but I didnt know where the line was between losing space and not gaining performance.

Also is stroking something I setup from the raid controller when the raid is created or is it done in the windows setup after the raid has been initialized?

Its too bad I dont have anymore room on my ICH10R for more in this RAID0. I will post screenshots when I get some hdtune, hdtach and everest disk tests
I'd set the first partition to 50GB, then you got some breathing space for the OS and programs. Leave the rest for games and storage.

Short-stroke just basically means having a smaller partition give the heads less space to move and in doing so, increases the seek times. All is done within the RAID BIOS. Windows knows nothing about the raid setup, it just treats as one device.
What I have read online after coming across short stroking has led me to see very different performance changes based on the % of the drive stroked, there was a toms hardware review that showed a difference of about 50mb/s or so just from stroking, I cant find the link right now.

I figured when you set the size of the partition in the RAID BIOS that it would stroke it, but somone commented about how they can use the other space not throwing away to the OS? If this is possible you can have the other 1.8tb for storage? wouldnt that slow down the performace?
using the rest of the disk can make performance much worse than not 'short-stroking' at all.
I got 1.8TB for storage at the minute. I did leave it dead space, but thought what the hell .. hehe

As for performance effects, as the "storage / games" partition is only accessed when you use that partition is has no affect on the OS drive. If it has, I can not tell if it is. As the partition is only accessed when I need to.. which is like.. hardly.

Also the 2nd partition will also be increased in speeds due to being in a RAID 0 setup, only when you get towards the end of the drive you will see performance drop, as you would with any mechanical drive .



Thats my 2nd partition of the drive, so it still pretty nippy.
See less See more
Short stroking is not a setting

All you do is make a partition very small and at the outermost space of the drives by making it the 1st created parition.

I used 6x 1tb caviar blacks to achieve 650MBPS read speeds and 7ms latency with a partition size of 500GB

Honestly though, my 1 120GB SSD that does 250MBPS read is so much faster in real world apps. If you don't need space, SSD is the best option.
I have no problem short stroking and dropping 1.7tb for performance, and never using that extra space.

If it degrades my raid0 there is no point in stroking in the first place
Quote:


Originally Posted by XFreeRollerX
View Post

Short stroking is not a setting

All you do is make a partition very small and at the outermost space of the drives by making it the 1st created parition.

I used 6x 1tb caviar blacks to achieve 650MBPS read speeds and 7ms latency with a partition size of 500GB

Honestly though, my 1 120GB SSD that does 250MBPS read is so much faster in real world apps. If you don't need space, SSD is the best option.

The solid state still performs faster? I cant believe that. Especially when it comes to write speed the RAID should blow it out of the water!

So when I stroke my RAID0 to 10% is that of the total 2TB or is that from the 1TB
See less See more
You don't short stroke to increase your read speeds. You short stroke to decrease your access times.

OS use generally requires lots of random I/O - so SSDs are king here. No mechanical disk setup can touch them. Once your sequential read speed is above say 100MB/s there is no difference any more - it is the random perfromance that matters.

As stated, if you only use the extra space on the disk for rarely used files then there is no problem. But if you EVER use a file on the 'slow' partition you force the read heads to track across the platter to reach that file - and this takes time. Exactly the time you are trying to reduce by short stroking in the first place. Using it for media storage is not so bad really, as the odd seek to read an mp3 will not have much impact, and you are unlikely to be doing anything else with your PC while watching a movie. Backup images are also a good choice to store on the extra space. But putting your games on the inner partition is a poor idea - the heads will spend time tracking back and forth between your partitions, taking more time than they would do if you just installed everything in a single partition, as the data will be further spread across the disk surface. No benchmark can show you this, and it is irrelevant what a bench of each individual array/partition shows you. Most OSes constantly read & write to the HDD, loading shared libraries & other background tasks etc, so even while gaming you still need OS access - and this is why short stroking and using the extra space for this type of data is a poor idea.

Now if you do video editing or other applications that do sustained, sequential reads or writes, then a high speed RAID0 array will blow away a single SSD - because now the raw sequential rate is most important. Some games also benefit from this as they load large textures.

There is no 'best' way to do storage - you have to tailor your setup to your usage. Synthetic benchmarks are also almost entirely useless to determine the fastest setup for any given situation. Mainly because most people don't know or don't understand the tests they are running and the results presented to them.
See less See more
  • Rep+
Reactions: 3
Quote:

Originally Posted by the_beast View Post
You don't short stroke to increase your read speeds. You short stroke to decrease your access times.

OS use generally requires lots of random I/O - so SSDs are king here. No mechanical disk setup can touch them. Once your sequential read speed is above say 100MB/s there is no difference any more - it is the random perfromance that matters.

As stated, if you only use the extra space on the disk for rarely used files then there is no problem. But if you EVER use a file on the 'slow' partition you force the read heads to track across the platter to reach that file - and this takes time. Exactly the time you are trying to reduce by short stroking in the first place. Using it for media storage is not so bad really, as the odd seek to read an mp3 will not have much impact, and you are unlikely to be doing anything else with your PC while watching a movie. Backup images are also a good choice to store on the extra space. But putting your games on the inner partition is a poor idea - the heads will spend time tracking back and forth between your partitions, taking more time than they would do if you just installed everything in a single partition, as the data will be further spread across the disk surface. No benchmark can show you this, and it is irrelevant what a bench of each individual array/partition shows you. Most OSes constantly read & write to the HDD, loading shared libraries & other background tasks etc, so even while gaming you still need OS access - and this is why short stroking and using the extra space for this type of data is a poor idea.

Now if you do video editing or other applications that do sustained, sequential reads or writes, then a high speed RAID0 array will blow away a single SSD - because now the raw sequential rate is most important. Some games also benefit from this as they load large textures.

There is no 'best' way to do storage - you have to tailor your setup to your usage. Synthetic benchmarks are also almost entirely useless to determine the fastest setup for any given situation. Mainly because most people don't know or don't understand the tests they are running and the results presented to them.
Great insight.

How about if you partition 250-500GB on a RAID0 1TB setup where the OS and applications are on the same partition while the rest is used for storage. Does it still suffer the same effect?
See less See more
I think 500GB would be to much to see any real benefit in seek times. I'd use the OS needs, your programs etc, the most played game. Say 100GB would be more than enough.

I use the 2nd partition only for storage at the minute whilst running various tests as I don't need the space. I've installed a few games on there and run (mostly Grid v1.3) and not noticed any improvements to load times be it on the OS drive or the storage drive.

I've next to test Crysis load level times, again one on the OS drive and one on the storage. I doubt there will be any difference in actual loading of the level, as once the level is loading, the OS ain't going to be doing much else. If there is, it will negligible i'd guess.

If you use the 2nd partition (the slow one) and also access the OS drive at regular intervals, then you will gain nothing.
See less See more
HAHAHAHAH wow dude your IOPS is so low compared to an SSD


I don't miss my 6-disk RAID 0 with Caviar black 1TBs

IOPS is what really affects real-world speeds.
See less See more
Indeed, it's going to be slow when compared to a SSD, how can it even compete?

This was just a bench for those seeking out RAID 0 performance on "Mechanical drives".

When I get my Corsair X32's in a RAID 0, obviously, it's going to be quicker but I didn't post the scores to "compete" with a SSD.

We all know the IOPS are important, but for those unfortunately not in grasp of a SSD, I think the performance is respectable.

The price of a single "decent SSD" is enough to put people off.
1 - 20 of 32 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top