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 MX100 512GB continues to upstage the pricier M550. Both sit just adrift of the front of the pack, well ahead of their 256GB counterparts.

Even the MX100 256GB is competitive with the equivalent M550, and it actually comes out ahead with reads. These lower-capacity units still have slower mean service times than the 512GB drives, though. They're particularly far behind with writes, and they're also not alone. The budget-priced Samsung 840 EVO 250GB and Crucial M500 240GB have even slower mean write service times.

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.

Crucial SSDs typically log more extremely long write service times than their peers in this test. The MX100 is a big improvement over the M500, but it still suffers way more sluggish write service times than SSDs from other vendors. (The Adata SP920 is just an M550 with a different sticker on the outside.)

At 512GB, the MX100 comes out ahead of the M550 with both reads and writes. The 256GB results are mixed; the MX100 exhibits fewer extremely long service times with reads, but it suffers more of them with writes.

DriveBench 2.0 comprises tens of millions of I/O requests, so don't read too much into the totals in the graphs. For the MX100 256GB, the number of service times over 100 milliseconds amounts to only 0.037% of read requests and 0.32% of writes.