SSD Write Endurance 25nm Vs 34nm

[Anvil]

Ao1

That is correct, there can be no TRIM on such writes, it takes a delete to trigger TRIM and that will not occur during such I/O.
If the testfile is full-span then one would expect a TRIM to return the drive to almost fresh state when the test-file is deleted, that is not always the case though.

@minpayne

WA = NAND writes / Host writes

We can't tell for sure that we have found NAND writes for any drives with the exception of the SandForce based drives where E9 shows actual writes to NAND.
MWI Exhausted in the first chart is not an estimate, it is the actual bytes written by the Host at the time of MWI exhaustion, as in MWI = "0".
There are 2 drives (that are currently running) that shows "unexpected" results and those are the 830 and the G1 (w/o TRIM), all the other drives are within a few "cycles" of the NAND spec.

I expect we can find out what's going on with the 830 but the reporting looks to be "faulty" during this test, as it looks to require a power cycle for the SMART attributes to update.

The 830 really is strange, if we can be sure that 177 raw value = wear leveling count or "P/E count" then it would mean that it has written 13K times it's own capacity which would mean > 750TiB when Host writes shows that 200TiB has been written.


@Christopher
I was thinking the same as you , looking at the figures the 830 looks a bit like a drive w/o TRIM.
It might need GC to kick in in order for TRIM do actually do it's work and it's not allowed that pause and so eventually it slows down.