Random Read/Write Performance

Arguably much more important to any PC user than sequential read/write performance is random access performance. It's not often that you're writing large files sequentially to your disk, but you do encounter tons of small file reads/writes as you use your PC.

To measure random read/write performance I created an iometer script that peppered the drive with random requests, with an IO queue depth of 3 (to add some multitasking spice to the test). The write test was performed over an 8GB range on the drive, while the read test was performed across the whole drive. I ran the test for 3 minutes.

The three hard drives all posted scores below 1MB/s and thus aren't visible on our graph above. This is where SSDs shine and no hard drive, regardless of how many you RAID together, can come close.

The two Intel drives top the charts and maintain a huge lead. The OCZ Vertex actually beats out the more expensive (and unreleased) Summit drive with a respectable 32MB/s transfer rate here. Note that the Vertex is also faster than last year's Samsung SLC drive that everyone was selling for $1000. Even the JMicron drives do just fine here.

If we look at latency instead of transfer rate it helps put things in perspective:

Read latencies for hard drives have always been measured in several ms, but every single SSD here manages to complete random reads in less than 1ms under load.

Random write speed is where we can thin the SSD flock:

Only the Intel drives and to an extent, the OCZ Vertex, post numbers visible on this scale. Let's go to a table to see everything in greater detail:

4KB Random Write Speed  
Intel X25-E 31.7 MB/s
Intel X25-M 23.1 MB/s
JMicron JMF602B MLC 0.02 MB/s
JMicron JMF602Bx2 MLC 0.03 MB/s
OCZ Summit 0.77 MB/s
OCZ Vertex 2.41 MB/s
Samsung SLC 0.53 MB/s
Seagate Momentus 5400.6 0.81 MB/s
Western Digital Caviar SE16 1.26 MB/s
Western Digital VelociRaptor 1.63 MB/s

Every single drive other than the Intel X25-E, X25-M and OCZ's Vertex is slower than the 2.5" Seagate Momentus 5400.6 hard drive in this test. The Vertex, thanks to OCZ's tweaks, is now 48% faster than the VelociRaptor.

The Intel drives are of course architected for the type of performance needed on a desktop/notebook and thus they deliver very high random write performance.

Random write performance is merely one corner of the performance world. A drive needs good sequential read, sequential write, random read and random write performance. The fatal mistake is that most vendors ignore random write performance and simply try to post the best sequential read/write speeds; doing so simply produces a drive that's undesirable.

While the Vertex is slower than Intel's X25-M, it's also about half the price per GB. And note that the Vertex is still 48% faster than the VelociRaptor here, and multiple times faster in the other tests.

Sequential Read/Write Performance SYSMark 2007
POST A COMMENT

235 Comments

View All Comments

  • KadensDad - Tuesday, October 27, 2009 - link

    How do these drives fail? I have heard that they will just suddenly die, no more writes or reads possible. What I would like to know is what happens when it dies? Do you lose all data? Just can't write anymore? How does the OS respond? Any early warnings? What about e.g. CRC? How does possibility of data corruption compare to traditional SSD? What about RAID? Since the drives are electrical, not mechanical, this reduces the number of failure vectors and environmental concerns (e.g., ambient temperature over lifetime of the drive). Won't SSDs therefore fail closer together in time in a RAID configuration? This reduces the window of opportunity for fixing an array and also decreases the applicability of RAID, however marginal.
    Reply
  • adsmith82 - Monday, September 14, 2009 - link

    I need to run HDDErase on an X25-M. No matter what bootable CD or flash drive I create, HDDErase does not see either of my SATA hard drives. I already disabled AHCI in BIOS. Also, I am using version 3.3. I know that 4.0 does not work with the X25-M.

    Can someone help me troubleshoot this please? Thanks.
    Reply
  • gallde - Thursday, June 11, 2009 - link

    You point out that TRIM will only work on deletions, not on overwrites. But, couldn't a smart controller look at blocks that have a majority of invalid pages and "trim" them as well, recovering clean pages as a background process? Reply
  • forsunny - Thursday, August 13, 2009 - link

    Why not just make the SSDs capable of individual page erases instead of blocks? Problem solved. Reply
  • lyeoh - Friday, May 29, 2009 - link

    Good and informative article.

    Regarding the shill tshen83 who claims that Anandtech cost the drive manufacturers millions of dollars in sales.

    If that is true, Anandtech has saved customers millions of dollars.

    Anandtech should care more about their readers losses than drive manufacturer losses. If Anandtech was a site for drive manufacturers and their shills we wouldn't be reading it.

    To me, if the SSD drive manufacturers lose money, it's their own fault for building crap that has higher write latencies than old fashioned drives with metal discs spinning at 7200RPM or slower. Not anandtech's.

    I can get higher sequential reads and writes by using RAID on old fashioned drives. It is much harder to get lower latency. So Anandtech did the right thing for OCZ.

    Lastly, there might be a way of making your windows machine stutter less even with a crap SSD. Note: I haven't tested the actual effect on an SSD because I don't have an SSD.

    Basically by default when Windows accesses a file on NTFS, it will WRITE to the directory the time of the access. Yep, it writes when it opens files and directories (which are just special files). That might explain the stuttering people see. For a lot of things, Windows has to open files.

    Warning! There are reasons why some people or programs would want to know the last access time of files. Me and my programs don't (and I doubt most people would).

    If you are sure that's true for you (or are willing to take the risk) set NtfsDisableLastAccessUpdate=1 as per:

    http://technet.microsoft.com/en-us/library/cc75856...">http://technet.microsoft.com/en-us/library/cc75856...
    Reply
  • poohbear - Sunday, April 26, 2009 - link

    Brilliant article and very informative on these emerging technology. I wont be buying one anytime soon @ their prices, but good to know we'll FINALLY be replacing convential HDD which are the one component that have been pretty much the same since as far back as i can remember

    "SSDs have +5 armor immunity to random access latency"

    rofl that's the best analogy i've seen on a hardware review site. is every comp geek a RPG geek @ heart?
    Reply
  • Gootch - Sunday, April 19, 2009 - link

    Great article. Realy made me understand what I need to look at before making the plunge. Mistakes and all, my compliments. As for value between the now seemingly drastically improved Vertex vs the X25-M, I compared prices between the two and per Gb, the Intell product for say an 80 Gb drive is Can $5.86/Gb, while the OCZ 60 Gb SSD is Can $6.81/Gb. Now that we are no longer comparing apples and oranges, I think we need to point out that the Intel product is not only faster and maintains it's performance edge better, but it is cheaper per Gb. At least in Canada. I have many OCZ products and I love the company and it's customer support. I can only hope that they will make their SSDs more competitive in the near future, because most consumers will pay the extra 70 bucks and go with the X25 when they pay attention to the numbers, both performance and price. Reply
  • Baffo - Saturday, April 11, 2009 - link

    I could forsee a whole host of issues with encrypting SSD drives, not the least of which is essentially making the drive completely "used" outside of the drive slack space - which would be a temporary reprieve for the reasons discussed in this article. However, I could also see potential performance and lifetime issues since modern encryption uses streaming ciphers (e.g. an entire encrypted block - which may or may not conform to the physical block size will be changed for even one bit change within the block itself). Has anyone looked at the resultant effect on performance due to using encryption - it would be good to compare say Bitlocker, PGP, Checkpoint, and an open source encryption solution (Crypt or something like that?). This could actually become a real driver for moving to on-drive encryption where it would have the opportunity to optimize the encrpytion for the pro/cons of the SSD architecture. Reply
  • brandensilva - Friday, April 10, 2009 - link

    Great article! I respect that OCZ made the necessary changes to make this drive work. I'd rather take a slightly slower drive if it meant consistent performance.

    If my hard drive started to stutter I'd flip out! I'm glad that they took the feedback and instead of selling faulty drives, that would ultimately hurt their brand, they decided to go back to the drawing board and iron out the kinks. I'm not expecting them to compare to Intel's 25-M per price or performance. They don't have nearly the cash or manufacturing capacity to compete with Intel but they do have that small business feel with receiving feedback and making improvements, which is important to customers.

    Lets hope they continue to utilize that aspect of their business and further improve on their products and bring us some reliable SSD's in the future.
    Reply
  • Hrel - Thursday, April 09, 2009 - link

    although, I have some issues which I have put in an e-mail sent to Anand; can't wait for you response. Reply

Log in

Don't have an account? Sign up now