SSD Write Endurance 25nm Vs 34nm

[groberts101]

if Ao1 wasn't able to restore the V2 with a secure erase then there are other issues at play there. I would do a secure erase and test it as secondary using a quick sequential test with AS SSD. Even a hammered state drive would never go much below 50% of original fresh write speeds as the on the fly recovery is sufficient enough to keep from dropping below that.

These controllers implement a lifetime throttle called a settled in state when the Durawrite mapping has fully formed(all nand written to at least once). A proper SE will wipe that map completely and allow fresh speeds immediately afterwards. If it doesn't?.. something else going on there.

The other thing that needs to be kept in mind about Sandforce is the need for some idle time as TRIM alone will not initiate recovery as other controllers would do. SF needs that low activity idle time for the controller to recover those trim marked blocks more efficiently.

Also consider that if a Sandforce drive is barraged with random data like that it can take quite some time to rotate data and work towards improving internal data consolidation to allow any future writes to even have the slightest chance at being written contiguiously(which the controller tries to do whenever possible/within wear leveling's requirements. IOW,.. I've seen many that become far too fragmented(well..even moreson that usual for SSD) and can suffer badly. Still never seen one drop much below 50% of fresh incompressible write speeds though, and something seems odd given that the drive didn't respond to the SE as expected. I'd be trying it on another machine as a freshly SE'd/quick formatted secondary drive and I would guess that would help paint a truer picture.

How was the SE done and with what tool?