Sequential Read/Write Speed

To measure sequential performance I ran a 3 minute long 128KB sequential test over the entire span of the drive at a queue depth of 1. The results reported are in average MB/s over the entire test length.

Iometer - 128KB Sequential Write

Sequential write speed is much higher than Kingston’s previous offerings. Compared to the old V+ there’s very little performance difference here. The new V+ 100 does well even against SandForce and Crucial based SSDs. In fact, if you write incompressible data to the SandForce drives the V+ 100 is the fastest SSD in sequential writes at this capacity.

The 64GB Crucial RealSSD C300 does a respectable 71MB/s here, which isn’t bad for a low capacity value drive. Sequential write speed is equal to Corsair’s F40 when writing incompressible data (e.g. compressed movies or pictures), and better than both the 40GB X25-V and 30GB Kingston SSDNow V Series.

Iometer - 128KB Sequential Read

The V+ 100‘s sequential read speed is excellent, just a hair above the top drives from Intel and Crucial. There’s not much room for improvement here unless you go to a 6Gbps interface. Although not displayed here, the Crucial RealSSD C300 on a 6Gbps SATA interface is the single-drive sequential read speed king.

The 64GB C300 loses no performance as a result of its lower capacity, making it the best low capacity drive for sequential read performance.

Overall Iometer shows us that the four corners of SSD performance are not dominated by any one controller/firmware combination. Crucial takes the clear lead in random read performance, while the Toshiba based SSDNow V+ 100 is the 3Gbps sequential read king. Random write performance depends mostly on what you’re writing. If you’re writing highly compressed data like movies and pictures, then Crucial is the undisputed champ there as well. If you’re writing documents, emails and other highly compressible data, SandForce based drives like the Corsair Force and OCZ Vertex 2 are the drives to beat.

With no silver bullet, we have to look at various desktop workloads to really measure the performance of these drives.

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

96 Comments

View All Comments

  • dagamer34 - Saturday, November 13, 2010 - link

    If you're buying an SSD, I see no reason why your OS should still be Windows XP.
  • Oxford Guy - Sunday, November 14, 2010 - link

    Some may not want to pay the Microsoft tax.
  • Out of Box Experience - Monday, November 15, 2010 - link

    What you see is irrelevant to what I use!

    I see several good reasons to use XP and None to using Windows 7

    The number 1 OS is still XP and has the highest user base so why does OCZ think the public will spend an extra $200 for Windows 7 just to use their overhyped SSD's?

    Why doesn't OCZ just build SSD's for the majority of people on XP instead of making their customers jusmp though all these hoops just to get synthetic speeds from their drives that have little to do with real world results?
  • sprockkets - Sunday, November 21, 2010 - link

    Oh, I don't know, TRIM support, built in alignment support, build in optimization after running WEI for SSDs?

    But if you want to stick with a 9 year old OS which lacks basic security, poor desktop video rendering, etc, go right on ahead.
  • Anand Lal Shimpi - Thursday, November 11, 2010 - link

    Representing the true nature of "random" access on the desktop is very difficult to do. Most desktops don't exhibit truly random access, instead what you get is a small file write followed by a table update somewhere else in the LBA space (not sequential, but not random). String a lot of these operations together and you get small writes peppered all over specific areas of the drive. The way we simulate this is running a 100% random sweep of 4KB writes but constraining it to a space of about 8GB of LBAs. This is overkill as well for most users, however what the benchmark does do is give an indication of worst case small file, non-sequential write performance. I agree with you that we need more synthetic tests that are representative of exactly what desktop random write behavior happens to be, however I haven't been able to come across the right combination to deliver just that. Admittedly I've been off chasing phones and other SSD issues as of late (you'll read more about this in the coming weeks) so I haven't been actively looking for a better 4KB test.

    Now OS X feeling snappier vs. SandForce I can completely agree with. I don't believe this is 100% attributable to the data you see here, Apple also has the ability to go in and tweak its firmwares specifically for its software. I believe the ultra quick response time you see from boot and resume comes from firmware optimizations specific to OS X. Although I am going to toss this Kingston drive in my MBP to see what things look like at that point.

    Take care,
    Anand
  • iwodo - Friday, November 12, 2010 - link

    ARH, Thx,

    "toss this Kingston drive in my MBP to see what things look like at that point."

    I never thought of that. Keep thinking mSATA was blocking anyone from testing it.

    I am looking forward to see your SSD issues and MBP testing.

    Tech news has been dull for number of years, SSD finally make thing interesting again.
  • sunjava04 - Friday, November 12, 2010 - link

    hey anand,

    would you provide a different SSD test result with macbook pro?

    like me, many macbook unibody or new mac book pro users use mainly for browsers and office, iphoto, itunes. we like to have ssd to make our experience better and faster. i search many website and blogs, but there are no clear answer for this.
    even, apple keeping quite about "TRIM" support!

    after, reading your article, i am still not sure which ssd is good for my macbook unibody. i got the an idea of garbage collection which was very helpful. but didn't know, how long ssd last if we use for general purpose?

    i really appreciate if you provide descriptive guideline of ssd for OS X.
    please, also tell us, is it worth to waiting for intel 3rd gen.?
    i desperately need ssd for mac book unibody!
    i dont mind to pay premium as long as performance stay as it is! also, i can store movies and other data in external hard drive!

    Sincerely,
    Rishi
  • iwodo - Saturday, November 13, 2010 - link

    As of Today, i just read another review on SSD comparison. Namely Intel SSD and Sandforce,

    While the Sandforce wins on all synthetic benchmarks like Seq Read Write and Random Read Write.

    It was booting slower, starting up Apps slower, finish task slower then Intel SSD.
    And by an noticeable amount of percentage. ( 10 - 30% )

    I am beginning to think there are things Sandforce dont work well at all. But again, we have yet to find out what.
  • Out of Box Experience - Tuesday, November 16, 2010 - link

    Sandforce controllers give you the "illusion" of speed by writing less data to flash than contollers without hardware compression

    If I wanted to test the speed of a copy and paste involving 200MB of data in the flash cells of a sandforce based controller, how can I tell exactly how much data is in the flash cells?

    I mean, would Windows tell me how much compressed data is represented in the flash cells (200MB), or would Windows tell me how much compressed data is in the cells (maybe only 150MB) ?

    The only way I can see fairly comparing an SSD with hardware compression and one without is to be sure you are actually writing the same amount of data to the flash cells (in this case - 200MB)

    If sandforce based SSD's will only tell you how much data is represented and not what is actually on the drive, then I think the best way would be to use data that cannot be compressed

    The tests I described in another post here involved copying and pasting 200MB of data which took 55 seconds on an ATOM computer with a Vertex 2
    200MB / 55 sec = 3.6MB/sec

    But if the 200MB was only a representation and the actual amount of data was for example 165MB in flash, then the actual throughput of my Vertex was even worse than I thought (In this case - 165MB / 55sec = 3.0MB/sec)

    I need to know exactly how much data is indeed in flash or I need to start using non-compressible data for my tests

    Make sense?
  • Out of Box Experience - Monday, November 15, 2010 - link

    There has to be an missing pieces in our performance test, something that these companies knows and we dont.
    ------------------------------------------

    Like smoke & Mirrors?

    Sandforce Controllers Compress the data to give you the impression of speed

    check the speed without compression and then compare drives

Log in

Don't have an account? Sign up now