Random Read/Write Speed

This test reads/writes 4KB in a completely random pattern over an 8GB space of the drive to simulate the sort of random access that you'd see on an OS drive (even this is more stressful than a normal desktop user would see). I perform three concurrent IOs and run the test for 3 minutes. The results reported are in average MB/s over the entire time.

I've had to run this test two different ways thanks to the way the newer controllers handle write alignment. Without a manually aligned partition, Windows XP executes writes on sector aligned boundaries while most modern OSes write with 4K alignment. Some controllers take this into account when mapping LBAs to page addresses, which generates additional overhead but makes for relatively similar performance regardless of OS/partition alignment. Other controllers skip the management overhead and just perform worse under Windows XP without partition alignment as file system writes are not automatically aligned with the SSD's internal pages.

First up is my traditional 4KB random write test, each write here is aligned to 512-byte sectors, similar to how Windows XP might write data to a drive:

4KB Random Write - MB/s

In sector-aligned 4K random writes, nothing is faster than our X25-V RAID 0 array. We're talking faster than Intel's X25-E, faster than SandForce...you get the picture.

Our 4K aligned test, more indicative of random write performance under newer OSes puts a damper on the excitement:

4K Aligned - 4KB Random Write - MB/s

At 71.6MB/s we're definitely faster than any other Intel drive here, as well as the 50GB SandForce offerings. But still no where near as fast as the C300 or OCZ Vertex LE.

Random read performance didn't improve all that much for some reason. We're bottlenecked somewhere else obviously.

Sequential Read/Write Speed Overall System Performance using PCMark Vantage
Comments Locked

87 Comments

View All Comments

  • Makaveli - Tuesday, March 30, 2010 - link

    Why are so many of you having difficultly understanding this. YOU DO NOT GET TRIM SUPPORT WITH THE NEW INTEL DRIVERS IF YOU HAVE A RAID ARRAY BUILT OF JUST SSDs!

    Where every you guys are reading that stop its wrong!

  • vol7ron - Tuesday, March 30, 2010 - link

    Finally a RAID! Thank you, thank you, thank you. Just a few days too late before I bought the 80GB, but still this makes your review a little more meaningful - it is essentially the equivalent of showing overclocks for CPUs and more meaningful, since HDs are a bottleneck.

    Advice:
    RAID-0s see a greater impact with 3 or more HDs. I think the impact is exponential to the number of drives in the array, not just seemingly double. I know TRIM is not supported, but if you could get one more 40GB drive and also include the impact, that would be nice - I would consider anything more than 3 drives in the array as purely academic; 3 or less drives is a practical (and realistic) system setup.


    Notes to others:
    I saw the $75 discount on Newegg for 80GB X25MG2 (@ $225) and decided to grab it, since one of my 74GB Raptors finally failed in RAID. This discount (or price drop) is most likely due to the $125 40GB version. I also picked up Win7 Ultimate x64, to give it a try.
  • cliffa3 - Tuesday, March 30, 2010 - link

    Anand,

    On an install of Win7, I'm guessing a good bit of random writes occur.

    How much longer would you stave off the performance penalty due to having no TRIM with RAID if you took an image of the drive after installation, secure erased, and restored the image?

    Please correct me if I'm wrong in assuming restoring an image would be entirely sequential.

    I would probably image it anyway, but just trying to get a guess on what you think the impact would be in the above scenario to see if I should immediately secure erase and restore.

    I also would be interested in how much improvement you get by adding another drive to the array in RAID 0...is it linear?
  • GullLars - Tuesday, March 30, 2010 - link

    Some of the powerusers i know have used the method of secure erase + image to restore performance if/when it degrades. Mostly they do it after heavy benchmarking or once every few months on their workstations (WMvare, databases and the like).

    RAID scales linearly as long as the controller can keep up. This is the RAW performance numbers, the real life impact is not linear, and will have diminishing returns due to storage performance being divided in two major categories: Throughput and accesstime. Throughput scales linearly, accesstime stays unchanged. Though average accesstime for larger blocks and under heavy load takes less of a hit in RAIDs.

    Intels southbridges scale to roughly 600-650MB/s, and i've seen 400+ MB/s done at 4KB random.

    As for random read scaling in RAID, you have the formula IOPS = {average accesstime} * {Queue Depth}
    Average accesstime has a more gentle slope in RAID as the Queue Depth scales the more units you put in the RAID, but at low QD (1-4) there is little to gain for blocks smaller than stripe size. No matter how may SSDs you add in the RAID, you will never get scaling more than QD * IOPS @ QD 1.
  • ThePooBurner - Tuesday, March 30, 2010 - link

    Check out this video of 24 SSDs in a raid 0 array. Mind blowing.

    http://www.youtube.com/watch?v=96dWOEa4Djs
  • GullLars - Tuesday, March 30, 2010 - link

    Actually, that RAID has BAD performance compared to the number of SSDs.
    You are blinded by the sequential read numbers. Those Samsung SSDs have horrible IOPS performance, and the cost of the setup in the video compared to performance is just outright awfull.

    You can get the same read bandwidth with 12 x25-V's, and at the same time 10X the IOPS performance.
    Or if you choose to go for C300, 8 C300 will beat that setup in every test and performance meteric you can think of.

    Here is a youtube video of the performance of a Kingston V 40GB launching 50 apps for you to compare to the Samsung setup:
    http://www.youtube.com/watch?v=sax5wk300u4&fea...

    I will also point out my 2 Mtron 7025 SSD that were produced in dec 2007 can open the entire MS office 2007 suite in 1 second, from SB650 and prefetch/superfetch deactivated.
  • Slash3 - Tuesday, March 30, 2010 - link

    Speaking of which, is there a "report abuse" button for comments on this new site design system? I didn't notice one, just in fumbling around a bit.
  • waynethepain - Tuesday, March 30, 2010 - link

    Would defragging the SSDs mitigate some of the build up of garbage?
  • 7Enigma - Tuesday, March 30, 2010 - link

    You do not defrag an SSD.
  • GullLars - Tuesday, March 30, 2010 - link

    You don't need to defrag a SSD, but you can. This does not affect the physical placement of the files, but will defragment their LBA fragmentation in the file tables. Since most SSDs can reach full bandwidth (or close to) at 32-64KB random read, you need a seriously fragmented system before you will notice anything. There are almost no files that will get fragmented into that small pieces, and even if you get 50 files each in 1000 fragments of 4KB, the SSD will read each one when they are needed in a fraction of a second.

    It doesn't hurt to defrag if you notice a few files in hundreds or thousands of fragments, the lifespan of the SSD will be unaffected by one defrag a week, but it will cause spikes of random writes, wich may cause a _temporary_ performance degrading if you don't have TRIM.

Log in

Don't have an account? Sign up now