Plextor M6S & M6M (256GB) Review
Performance Consistency
Performance consistency tells us a lot about the architecture of these SSDs and how they handle internal defragmentation. The reason we don’t have consistent IO latency with SSD is because inevitably all controllers have to do some amount of defragmentation or garbage collection in order to continue operating at high speeds. When and how an SSD decides to run its defrag or cleanup routines directly impacts the user experience as inconsistent performance results in application slowdowns.
To test IO consistency, we fill a secure erased SSD with sequential data to ensure that all user accessible LBAs have data associated with them. Next we kick off a 4KB random write workload across all LBAs at a queue depth of 32 using incompressible data. The test is run for just over half an hour and we record instantaneous IOPS every second.
We are also testing drives with added over-provisioning by limiting the LBA range. This gives us a look into the drive’s behavior with varying levels of empty space, which is frankly a more realistic approach for client workloads.
Each of the three graphs has its own purpose. The first one is of the whole duration of the test in log scale. The second and third one zoom into the beginning of steady-state operation (t=1400s) but on different scales: the second one uses log scale for easy comparison whereas the third one uses linear scale for better visualization of differences between drives. Click the buttons below each graph to switch the source data.
For more detailed description of the test and why performance consistency matters, read our original Intel SSD DC S3700 article.
![]() |
|||||||||
| Plextor M6S | Plextor M5M | Crucial M550 | SanDisk Extreme II | Samsung SSD 840 EVO mSATA | |||||
| Default | |||||||||
| 25% Spare Area | |||||||||
Ouch, this doesn't look too good. The IOPS is constantly dropping below 1000, which is something I'm not expecting to see anymore. Even the M550 can keep the IOPS at ~4000 minimum, so the M6S certainly doesn't do well here. With added over-provisioning (OP) the performance does look a lot better and the minimum IOPS jumps to ~10K but it's still a downgrade from the M5M. Given the change to a lighter controller this is perhaps expected, but I'm still worried about the consistency without additional OP. I would make sure to leave ~10-15% of empty space with the M6S and M6M to avoid running into inconsistent performance.
![]() |
|||||||||
| Plextor M6S | Plextor M5M | Crucial M550 | SanDisk Extreme II | Samsung SSD 840 EVO mSATA | |||||
| Default | |||||||||
| 25% Spare Area | |||||||||
![]() |
|||||||||
| Plextor M6S | Plextor M5M | Crucial M550 | SanDisk Extreme II | Samsung SSD 840 EVO mSATA | |||||
| Default | |||||||||
| 25% Spare Area | |||||||||
Originally published at https://www.anandtech.com/show/7896/plextor-m6s-m6m-256gb-review (Wayback Machine).


