The Plextor M9Pe NVMe SSD Review: Teaching An Old Chip New Tricks
by Billy Tallis on May 24, 2018 1:00 PM ESTSequential Read Performance
Our first test of sequential read performance uses short bursts of 128MB, issued as 128kB operations with no queuing. The test averages performance across eight bursts for a total of 1GB of data transferred from a drive containing 16GB of data. Between each burst the drive is given enough idle time to keep the overall duty cycle at 20%.
The burst sequential read speeds from the Plextor M9Pe are worse than most NVMe SSDs including the low-end MyDigitalSSD SBX, but at least it's still well above SATA speeds (unlike the Plextor M8Se).
Our test of sustained sequential reads uses queue depths from 1 to 32, with the performance and power scores computed as the average of QD1, QD2 and QD4. Each queue depth is tested for up to one minute or 32GB transferred, from a drive containing 64GB of data.
On the longer sequential read test, the M9Pe fares a little better as the MyDigitalSSD SBX and Intel SSD 760p drop down to about the same level. As with the burst test, the Samsung drives dominate.
Power Efficiency in MB/s/W | Average Power in W |
The Plextor M9Pe's power efficiency on the sequential read speed is below average, but it's not actually the worst-scoring NVMe SSD for this test—that distinction belongs to the Intel SSD 760p, which is barely more efficient than the Crucial MX500 SATA SSD.
Both M9Pe models hit full sequential read speed at QD4, which is relatively late, but not as slow a ramp up as the WD Black shows.
Sequential Write Performance
Our test of sequential write burst performance is structured identically to the sequential read burst performance test save for the direction of the data transfer. Each burst writes 128MB as 128kB operations issued at QD1, for a total of 1GB of data written to a drive containing 16GB of data.
The burst sequential write speeds from the Plextor M9Pe are good, with only the WD Black and a few Samsung drives scoring better. The older generation of Plextor drives performed much worse on this test.
Our test of sustained sequential writes is structured identically to our sustained sequential read test, save for the direction of the data transfers. Queue depths range from 1 to 32 and each queue depth is tested for up to one minute or 32GB, followed by up to one minute of idle time for the drive to cool off and perform garbage collection. The test is confined to a 64GB span of the drive.
On the longer sequential write test, the M9Pe manages to stay ahead of the low-end NVMe drives but otherwise doesn't perform well. Capacity is a major factor in performance here: the 1TB model is 80% faster than the 512GB model.
Power Efficiency in MB/s/W | Average Power in W |
With almost average performance, the 1TB M9Pe has reasonable but not top-tier power efficiency on the sustained sequential write test. The 512GB model has the second-worst efficiency score out of this batch of drives.
The sequential performance of the Plextor M9Pe increases slightly from QD1 to QD2 and is steady thereafter, with no obvious signs of SLC write cache exhaustion or intermittent garbage collection getting in the way.
15 Comments
View All Comments
Yuriman - Thursday, May 24, 2018 - link
Looks like that heatspreader does it a lot of good.peevee - Tuesday, May 29, 2018 - link
But the price of it? I understand it for $4 on 256GB model. But why the same thing is closer to $40 on 1T?romrunning - Thursday, May 24, 2018 - link
Regarding the testing platform: "The Windows 10 version will still be 1709, because Microsoft has not yet fixed all the new bugs introduced in the NVMe driver in Windows 10 version 1803."If you're referring to the issues with Intel 600p drives in the April Update (version 1803), Microsoft released a new patch (KB4100403) that "Addresses an issue with power regression on systems with NVMe devices from certain vendors."
So it sounds like you should be able to update Windows to 1803 as long as you include that patch.
Billy Tallis - Thursday, May 24, 2018 - link
That's not the only problem that's been reported with 1803's NVMe driver. I don't trust that they've even found all the new bugs yet, let alone patched them all. And I actually started running the new tests almost a month ago, to try to minimize the interruption to our review schedule.Drazick - Thursday, May 24, 2018 - link
Are you sure it is Microsoft's issue and not the firmware of those drives?Billy Tallis - Thursday, May 24, 2018 - link
In the absence of a proper changelog from Microsoft, I assume the new issues are mostly their fault. At the very least, they're responsible for upsetting whatever fragile balance of bugs the SSD manufacturers have achieved by testing against previous versions of Windows 10. I want to freeze my testbed software configuration for at least a year, and there's sufficient reason to consider 1803 as still being essentially beta-quality and thus a bad choice for the 2018 SSD test suite.GeorgeH - Thursday, May 24, 2018 - link
FWIW that's very reasonable. It's utterly foolish to update to any Windows 10 version until at least 6 months after release (unless your time is worthless and you'd like to do free QA for Microsoft, of course).lmcd - Thursday, May 24, 2018 - link
Not even close to true. In fact, it's because I value my time that I upgraded to 1803 immediately. 1803 adds the "Windows Hypervisor Platform" to its features, which (as a primary effect) allows Docker for Windows and a buggy-but-usable Xamarin variant of AVD to run side-by-side (along with other Hyper-V images). It's possible we even see VirtualBox run on this excellent feature, though I don't know if it's on their roadmap yet.smilingcrow - Friday, May 25, 2018 - link
Which is an irrelevant feature for most home users so your post is myopic.Death666Angel - Friday, May 25, 2018 - link
If you are running normal consumer grade hardware, I don't think that is the case.