Single page Print

TR DriveBench 2.0 — Disk-intensive multitasking
DriveBench 2.0 is a trace-based test comprised of nearly two weeks of typical desktop activity peppered with intense multitasking loads. More details on are available on this page of our last major SSD round-up.

We measure DriveBench performance by analyzing service times—the amount of time it takes drives to complete I/O requests. Those results are split into reads and writes.

The BX100 surprises once again. Both versions have low mean service times for reads and writes. The MX200 500GB also fares well, but the 250GB exhibits clear weakness. It's not particularly quick with reads, and it's downright slow with writes.

The M600 256GB is even worse off, possibly because its higher capacity leaves less overprovisioned area for the controller. Dynamic Write Acceleration likely plays a role in the poor performance of both drives. DriveBench 2.0 squeezes an awful lot of writes into a relatively short span, and the caching scheme probably isn't tuned for such a heavy workload. Also, the idle time provided for garbage collection may be too short to allow the driver to transfer cached data to main storage.

All the SSDs execute the vast majority of DriveBench requests in one millisecond or less—too little time for end users to perceive. We can also sort out the number of service times longer than 100 milliseconds, which is far more interesting data. These extremely long service times make up only a fraction of the overall total, but they're much more likely to be noticeable.

These metrics paint a brighter picture of Dynamic Write acceleration, at least as it's employed in the MX200 250GB. That drive logs a fraction of the sluggish writes reported by the M600 256GB—and by the BX100. It's still a few orders of magnitude off the leaders, but it's a big improvement over Crucial's older SSDs.

The BX100 250GB suffers more slow writes than we'd like, especially compared to its 500GB twin. Again, though, Crucial has clearly outdone its previous offerings. The older MX100 has more service times over 100 milliseconds with both reads and writes.