SSD Write Endurance 25nm Vs 34nm

[Ao1]

I'm on Version 3 of the SSD slayer now.

I'm going to keep running it on the uncompressible option, otherwise this experiment will never end. I'm just coming up to 8TB and I'm still at 100%.

Some observations/ thoughts:

• When TRIM executes it seems to lock the drive until the command is finished.
• It seems that the hang duration whilst the TRIM command is being executed is the same, regardless if the data is compressed or not.
• It must be a bit tricky for the SF controller to translate the OS TRIM command to the compressed data on the SSD. Either way a TRIM command with an Intel SSD seems to be more seamless. Perhaps it TRIM's more frequently or it can do it without locking up the drive at the same time.
• SF throttling seems to only really effect sequential speeds and 4k random speeds at high queue depth. 4K reads @ QD1 seem unaffected, although 4K random writes take a hit.
• Strangely SF drives throttle both read & write sequential speeds (why reads?)
• Even in a throttled state the V2 is faster that the 320 & the X25-V. (based on what is being reported by Anvil's app).
• The X25-V and 320 are exhibiting near linear wear based on the SMART info.
• Either the V2 has significantly better wear levelling or the SMART data is not as accurate.

EDIT:

Not sure what happens in Zone B. The Loop finishes at point A. It appears to start a new loop, but a couple of seconds later it locks up. Anvil's graph shows the same peak just after the loop finishes, but there is then no delay as can be seen in zone C below. It's the same pattern every time and it only happens just after the new loop starts. Sometime more pronounced other times its less pronounced.

One_Hertz, any chance of running perfmon to see how the 320 handles it?