Performance Comparisons – Client QD Weighted
These results attempt to simplify things by focusing on what really matters – the Queue Depths that folks actually see when using these products. A dimension is eliminated from the previous charts by applying a weighted average to those results. The weights were derived from trace recordings of moderate to heavy workloads, which still ended up running closer to QD=1-2 even on a slower SATA SSD. The intent here is to distill the results into something for those wanting 'just the facts' to grab and go when making their purchasing decisions. Don't be alarmed by the low figures. Remember, these are low queue depths – the place where these SSDs actually operate when in use by those not just running benchmarks all day!
The focus here should be on the burst read (blue bars) performance, as that translates directly to how random reads will actually 'feel' when using the system. It's interesting to see how far behind the BX300 was in this particular metric, especially considering that its predecessor outpaced it! The MX500 does excellent here – within striking range of the Samsung 850 EVO and PRO. DO note, however, that the Intel 545s (same 3D TLC NAND) actually fares slightly better on reads but not on writes.
SATA SSDs generally just saturate the interface and call it a day. That said, there is still some variance, and the MX500 comes in close to the top across the board, with sequential reads just edging out over the 1TB Samsung 850 EVO!
For those curious how these results pan out in comparison to older / other SSDs, here are a couple of rather large charts for your viewing pleasure:
Now go back on those long
Now go back on those long lists of SSD tested and put a red box around the SSD being tested because that’s some haystack of results to visually search through to see where the drive being tested compares to all those others in that very long List.
You can see the 4k and 128kb
You can see the 4k and 128kb scores in the 2 top charts, take that score and scroll down till you get to it.
The SSD being tested is at
The SSD being tested is at the top of the abbreviated charts – above the longer charts.
Allyn Malventano, Regarding
Allyn Malventano, Regarding the TRIM issues, can Crucial fix the problem with a firmware update? Thanks.
Most likely, yes.
Most likely, yes.
Looks like a solid
Looks like a solid alternative to 850 evo..
Allyn, what do you think of a
Allyn, what do you think of a MLC SSD with TLC cache?
TLC is slower than MLC, which
TLC is slower than MLC, which itself is slower than SLC. Micron has SLC mode caching for their smaller MLC/TLC drives because it improves speed.
A TLC cache would hurt performance.
I have the 1TB MLC Crucial MX200, which has enough flash that it doesnt need an SLC cache, however i do use the Momentum Cache which uses system DRAM as a fast cache. Its a good idea if you have a UPS, which i do.
Interesting, I wonder if,
Interesting, I wonder if, with the BX line being the ultra cheap ones, we’ll see it move to 3D QLC NAND before long, sure it’ll be slower than the others, but it’ll be a butt tonne cheaper.
get back to us when they are
get back to us when they are at $.10 a GB
Maybe in 5 years
Maybe in 5 years
With regards to what Jon
With regards to what Jon Tanguy said in the video about Power Loss Immunity eliminating the need for banks of capacitors – they were pretty cool to look at: https://i.imgur.com/wVXxOre.jpg
How does it compare with
How does it compare with MX300?
One of my takeaways is (trim
One of my takeaways is (trim speed aside) the performance on this isn’t all that different from a Vector. And the Vector was a monster (an unsafe hotrod that blew a gasket if you cycled power at the wrong time) of a client drive when it came out and was MLC only. It’s nice to see a budget TLC drive isn’t completely compromised.
Went from a 256 gig c300 at
Went from a 256 gig c300 at launch to a 500gig mx100, I just might upgrade to a 1 terabyte mx500.
Things are getting a bit saturated.
MX500 2TB appears to be 25%
MX500 2TB appears to be 25% cheaper than the 850 EVO 2TB
Maybe the trim results are
Maybe the trim results are like that because Crucial MX500 NCQ (Native Command Queuing) TRIM is actually working unlike Samsungs SSDs which have broken NCQ TRIM (this is why 8xx series are blacklisted for NCQ TRIM in Linux kernel).
Is there any test you could do to confirm this? Maybe somehow try to disable NCQ TRIM and then run the tests again. Maybe even run MX500 and 850 EVO in IDE mode instead of AHCI to make sure that NCQ is not a factor.