Sign in with
Sign up | Sign in

Results: Random Performance

SanDisk A110 PCIe SSD: Armed With The New M.2 Edge Connector
By

We turn to Iometer as our synthetic metric of choice for testing 4 KB random performance. Technically, "random" translates to a consecutive access that occurs more than one sector away. On a mechanical hard disk, this can lead to significant latencies that hammer performance. Spinning media simply handles sequential accesses much better than random ones, since the heads don't have to be physically repositioned. With SSDs, the random/sequential access distinction is much less relevant. Data are put wherever the controller wants it, so the idea that the operating system sees one piece of information next to another is mostly just an illusion.

4 KB Random Reads

Testing the performance of SSDs often emphasizes 4 KB random reads, and for good reason. Most system accesses are both small and random. Moreover, read performance is arguably more important than writes when you're talking about typical client workloads.

SanDisk's A110 behaves a lot like the Extreme II. And that's logical, considering the similarities between both drives. Small random accesses are dependent on flash, controller, and firmware performance; they aren't bottlenecked by SATA. Samsung's 840 Pro approaches 100,000 4 KB read IOPS, but that's still just around 400 MB/s. The A110 manages to score a win at a queue depth of 32, just inching past 100,000 IOPS.

This M.2-based SSD is actually rated for up to 115,000 IOPS. Keep in mind that we're not using a platform with native support for it, though. Performance may vary due to our adapter. In production, we'd expect a notebook equipped with the A110 to fare similarly or better.

4 KB Random Writes

Random write performance is also exceptionally important, without question. Early SSDs didn't do well in this discipline, seizing up even in lightweight workloads. Newer SSDs wield more than 100x the performance of drives from 2007, but there's a point of diminishing returns in client environments. When you swap a hard drive out for solid-state storage, your experience improves. Load times, boot times, and system responsiveness all get better. If called upon, your SSD-equipped system could handle a lot more I/O than the spinning media you had in there before. With consumer workloads, it's more about getting to those operations faster, not necessarily handling more of them.

This is the first time we've questioned the A110's performance (or at least, it would be if we hadn't seen the same behavior twice before). SanDisk's nCache technology isn't designed to be peppered over a large LBA space for long periods of time. Because that's what we're doing, performance appears lower. Still, the drive offers up over 60,000 IOPS every second at higher queue depths.

Here's a break-down of the maximum observed 4 KB sequential read and write performance with Iometer:

The highest 4 KB reads we've tested come from the A110. It'd fare even better if we tested 4 KB random writes differently. The order the drives appear in our chart is determined by maximum combined read and write performance, which is frankly an arbitrary (but still valid) way of sorting.

Write Saturation

A saturation test consists of writing to a drive for a specific period of time with a defined workload. Technically, this is an enterprise-class write saturation test, where the entire LBA space of the SSD is utilized at a high-queue-depth random write.

Through the first 600 minutes writing at a queue depth of 32, SanDisk's SSD takes its sweet time settling in at a steady state. That's in part due to the fact that the A110 doesn't do so well writing against the entire 256 GB LBA space, so that initial high-speed fill doesn't quite materialize.

When we break out a time slice of the 10 hours we're showing, illustrating the write I/O in more detail, it's clear that the A110 does well, even without additional over-provisioning (which would leave more room to run garbage collection algorithms, lending to higher transactional performance with every block filled).

React To This Article