@devsk.. Throttling hits when ALL the nand have been written at least once and the Durawrite's GC map has been fully formed once more. While Sandforce/OCZ will often force feed most to believe that it's a lifespan saving algorithm?.. it just more of a limitation as to what the controller will do once it must differentiate between all it's interanl algorithms being introduced.

Think of it(lifetime throttle) as kind of like an "overhead loss".. rather than jsut a lifespan saving algorithm since the controller must TRIM, recover on the fly(if no fresh blocks remain), wear level and rotate data all at the same time. The "hammered state throttle" would definately be considered a lifesaving algorithm.

Far too much dramatization going on here. If you don't like it?.. don't use it. Simple as that and no one needs another consumer advocate posting claims of false advertising around here. Plenty of threads about that crap over at Anandtech if you're into that sort of thing. It just is.. what it is.