Skip to main content

Ten 60 GB SandForce-Based Boot Drives, Rounded-Up

4 KB Random Performance

Random Read Performance (background info)

Examples include antivirus scans and typing in Word

From what we've seen in testing, it can be more difficult to generate consistent data using SandForce-based SSDs than many competing drives. In some benchmarks, we note up to 50 MB/s swings at low queue depths during successive runs. Yet, if we take the median results, all of the 60 GB models collected for this story perform fairly similarly, regardless of their NAND interface. The only exception is Intel’s SSD 520, which achieves a 50 MB/s lead over the competition at queue depths between two and four.

Meanwhile, the 64 GB Samsung 830 falls behind the SandForce-based pack. Crucial's m4 performs respectably, nearly matching the SSDs being rounded-up today. We see one anomaly at a queue depth of four, where the 64 GB m4 falls behind by roughly 90 MB/s.

Random Write Performance, Compressible

Examples include email, file compression, and Web browsing

In general, all 60 GB SandForce-based SSDs perform within a fairly tight range when we measure performance using compressible random writes. The only clear leaders are the Vertex 3 and SSD 520, but they only differentiate themselves at queue depths between four and eight.

The 64 GB Crucial m4 and Samsung 830 fall further behind in this test. We'd expect that, though, considering neither controller benefits from compression in the same way as SandForce's.

  • mayankleoboy1
    As these drives are basically boot drives, i would have liked a test where you measure the total time taken to install a fresh wi7-sp1 on it and install updates and install a few softwares like

    Ms-Office
    Adobe pdf reader
    a web browser, a photo manipulating program
    a music/video player.
    Install a game from a ISO.
    An antivirus

    And all these apps should be installed from the SSD itself (meaning their setups should be on the SSD).Then you should test the startup and shutdown times.

    All these synthetic benchies dont make much sense, IMHO.
    Reply
  • mayankleoboy1
    I have found that when working with SSD's, single core CPU performance becomes a big bottleneck in some tasks.
    A lot of operations use only a single core and the SSD cant use its true potential. That is, the CPU cant process data as fast as the SSD can provide.
    This is just reverse of what happens in case of mechanical HDD's.
    Reply
  • acku
    http://www.tomshardware.com/reviews/ssd-520-sandforce-review-benchmark,3124-14.html

    You're not going to see a major difference.
    Reply
  • phamhlam
    mayankleoboy1I have found that when working with SSD's, single core CPU performance becomes a big bottleneck in some tasks.A lot of operations use only a single core and the SSD cant use its true potential. That is, the CPU cant process data as fast as the SSD can provide.This is just reverse of what happens in case of mechanical HDD's.
    Well, it is pointless though since everything you are doing is so fast that it doesn't matter anymore. I however see your point since I can be loading a program and my SSD is not even at max speed my CPU frequency is maxed out. The only way to get more speed is to just overclock as much as you can.
    Reply
  • mayankleoboy1
    ackuhttp://www.tomshardware.com/review 24-14.htmlYou're not going to see a major difference.

    that is the point of buying a cheaper SSD based on a chepaer NAND.
    Reply
  • compton
    Considering the conclusion that performance is defined by flash, I find it interesting that the one SF2281 with Toggle NAND at 60GB is not in the roundup (in North America anyway). The Mushkin Chronos Deluxe 60 is substantially cheaper now at $99. It's performance characteristics are much more profound than the 25nm ONFI sync/async models. They're often out of stock at Newegg, and for good reason.

    Reply
  • clownbaby
    Is there a benchmark to compare virtual memory performance? My current workstation has 24gb of memory, which means Windows eats up 36gb of my boot drive for virtual memory. (yes, I know I can change/disable it, but some programs act wonky when it's screwed with). A dedicated virtual memory drive would free up space on my primary ssd, as well as keep the writes down.

    I'd also like to see small drives benchmarked as swap drives in video editing machines. Currently I'm using a raid 0 array of 1tb samsung drives that keeps up well enough, but I'd be interested to see if there are tangible productivity differences.
    Reply
  • fwiw...intel uses its own premium binned 25nm sych...that why 4k read were so good.
    Reply
  • JackNaylorPE
    With a final page heading "Performance Is Defined By Flash" I would have like to see that difference looked at more closely. For example, the Mushkin Chronos Deluxe uses premium 3Xnm Toshiba Toggle Mode Flash (as does Patriot Wildfire, Vertex 3 Max IOPS and OWC Mercury Extreme Pro) and I would love to see for example how just changing the Flashin in an SSD from the same manufacturer and line (i.e Chronos standard versus Deluxe, Vertex 3 versus Vertex 3 Max IOPS). With that info, a user can decide whether it's makes sense to invest in say the premium Toshiba stuff as compared to the "same SSD w/o the premium Flash. That was what I expected to see when I read the referenced page heading.
    Reply
  • jsowoc
    I'm wondering why Toms' own trace-based benchmark didn't make it into this round-up? Does it take much longer to run than the other tests? While comparing synthetics is important to determine why a certain drive behaves a certain way, trace-based benchmarks (PCMark 7 could be considered trace-based) is what makes the final purchasing decision. In this case, PCMark was the one with the most clear-cut differences, ones that would likely be mirrored in a trace-based benchmark.

    For a future SSD review/roundup could you take, for example, 10 real-life traces from 10 different editor's machines (the more variation in workload, the better), and then compare the %change in execution time vs. a reference drive?
    Reply