Random Read Performance

One of the major changes in our 2015 test suite is the synthetic Iometer tests we run. In the past we used to test just one or two queue depths, but real world workloads always contain a mix of different queue depths as shown by our Storage Bench traces. To get the full scope in performance, I'm now testing various queue depths starting from one and going all the way to up to 32. I'm not testing every single queue depth, but merely how the throughput scales with the queue depth. I'm using exponential scaling, meaning that the tested queue depths increase in powers of two (i.e. 1, 2, 4, 8...). 

Read tests are conducted on a full drive because that is the only way to ensure that the results are valid (testing with an empty drive can substantially inflate the results and in reality the data you are reading is always valid rather than full of zeros). Each queue depth is tested for three minutes and there is no idle time between the tests. 

I'm also reporting two metrics now. For the bar graph, I've taken the average of QD1, QD2 and QD4 data rates, which are the most relevant queue depths for client workloads. This allows for easy and quick comparison between drives. In addition to the bar graph, I'm including a line graph, which shows the performance scaling across all queue depths. To keep the line graphs readable, each drive has its own graph, which can be selected from the drop-down menu.

I'm also plotting power for SATA drives and will be doing the same for PCIe drives as soon as I have the system set up properly. Our datalogging multimeter logs power consumption every second, so I report the average for every queue depth to see how the power scales with the queue depth and performance.

Iometer - 4KB Random Read

Despite having NVMe, the SSD 750 doesn't bring any improvements to low queue depth random read performance. Theoretically NVMe should be able to improve low QD random read performance because it adds less overhead compared to the AHCI software stack, but ultimately it's the NAND performance that's the bottleneck, although 3D NAND will improve that by a bit.

Intel SSD 750 1.2TB (PCIe 3.0 x4 - NVMe)

The performance does scale nicely, though, and at queue depth of 32 the SSD 750 is able to hit over 200K IOPS. It's capable of delivering even more than that because unlike AHCI, NVMe can support more than 32 commands in the queue, but since client workloads rarely go above QD32 I see no point in test higher queue depths just for the sake of high numbers. 

 

Random Write Performance

Write performance is tested in the same way as read performance, except that the drive is in a secure erased state and the LBA span is limited to 16GB. We already test performance consistency separately, so a secure erased drive and limited LBA span ensures that the results here represent peak performance rather than sustained performance.

Iometer - 4KB Random Write

In random write performance the SSD 750 dominates the other drives. It seems Intel's random IO optimization really shows up here because the SM951 doesn't even come close. Obviously the lower latency of NVMe helps tremendously and since the SSD 750 features full power loss protection it can also cache more data in DRAM without the risk of data loss, which yields substantial performance gains. 

Intel SSD 750 1.2TB (PCIe 3.0 x4 - NVMe)

The SSD 750 also scales very efficiently and doesn't stop scaling until queue depth of 8. Note how big the difference is at queue depths of 1 and 2 -- for any random write centric workload the SSD 750 is an absolute killer.

AnandTech Storage Bench - Light Sequential Performance
Comments Locked

132 Comments

View All Comments

  • mmrezaie - Thursday, April 2, 2015 - link

    finally it has started, although I wont budge now. maybe next generation.
  • blanarahul - Thursday, April 2, 2015 - link

    Hey Kristian, I read that the 1.2 TB model uses 84 dies. But that's not a multiple of 18. So what gives? Is it running in 14 channel mode or something?
  • blanarahul - Thursday, April 2, 2015 - link

    Okay so it has 86 dies. But now it's even more confusing. Aren't they supposed be multiples of number of channels the controller is using?
  • SunLord - Thursday, April 2, 2015 - link

    Its likely 18 channels so 4 probably only address 4 dies while the 14 other channels handle 5
  • woggs - Thursday, April 2, 2015 - link

    yep
  • TyrDonar - Friday, April 10, 2015 - link

    Controllers don't have to operate on a specific multiple of the number of dies. That's just a coincidence as to how we've seen them so far on most SSD's. They can operate with varying priorities and asymmetrically. Further, more than 1 channel can address the same die in different intervals/priorities. As controllers become more and more complex, this kind of assymetrical operation will become more common, unfortunately this is correlated with increasing number of total dies and lower reliability.
  • huaxshin - Thursday, April 2, 2015 - link

    Will there be any M2 SSDs from Intel with NVMe? Some notebooks, and desktops, have routed PCIe to M2 slots where its the only place its available.
  • blanarahul - Thursday, April 2, 2015 - link

    No.
  • DigitalFreak - Thursday, April 2, 2015 - link

    Not with this controller. Maybe down the road.
  • bgelfand - Thursday, April 2, 2015 - link

    I suspect this drive is not for the current z97 chip set, but will realize its potential with the Z170 chipset (Sunrise Point) due for release in the second half of this year with Skylake. The Z170 chipset has 20 PCIe 3.0 lanes and DMI 3.0 (8 GB/s) bus interface.

    It should be a very interesting second half of the year - Skylake CPU, Sunrise Point chipsets, and Windows 10.

Log in

Don't have an account? Sign up now