Performance Comparisons – Sequential and Random
Just as we did on the last page, I'll start us off with Sequentials:
Recall that all data points here are the result of cumulative sampling across multiple percentages of allocated space. If you see what looks like an outlier or a weird dip, rest assured that apparent aberration was repeatable and consistent.
SATA SSDs have mostly equalized at saturated interface-limited performance, but some of the older parts here come in a bit lower than the more modern units. The BX300 appears to be the lowest performance, with the Intel 545s showing a hitch at QD=1.
Now for random:
While typical usage rarely exceeds QD=8, we extend these charts out to 256 for PCIe / NVMe reviews (QD=32 for SATA) to evaluate manufacturers claimed performance maximums. Our exclusive burst test is the only way to properly evaluate the random write performance of caching SSDs. Note how the majority of SSDs all start at a relatively low value at lower queue depths. The BX300 is particularly weak in random writes but keeps up in reads. Let's move onto the next page to get a better idea of exactly where these drives fall head to head.







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.