this is about the easiest way to learn about the lazy recovery associated with trimmed blocks on this controller. Has to do with the first gen mostly but has the same exact basic function on this newer 6G controller. This newest SF-2281 just has a larger recycling engine(which it would surely need for faster throughput) and can be called more efficient in all aspects mentioned in this link.
http://www.ocztechnologyforum.com/f...ives-TRIM-OP-area-use-and-Life-write-throttle
So, in a nutshell here?.. this controller can mark those blocks in real-time just as any other controller will do. BUT.. decides to actually set those trim-marked blocks aside for later recovery during lower activity states(hence the idle time rec's). A lazy-trim.. so to speak.
Just because the controller trims those blocks in near immediate fashion has not much to do with when it decides to clean and return them back to the fresh block pool. That's why you can't simply TRIM an entire SF drive and expect it to release it all back to be used immediately and never become throttled.
GC time also allows the little known partial block consolidation algorithm to free up even more space and can be thought of as a free space consolidation/physical space defrag of sorts. These facts alone are what makes GC king on any Sandforce controlled drive. I've been running for nearly 1.5 years without TRIM being needed at all and the very existence of IBIS/Revo drives should point out that it can be done for the longterm.
GC time is THE number one thing I recommend to any who run a Sandforce controlled drive. Next in line would be to do away with all sleep/hibernate modes to be sure the drive doesn't act up if the power transitions don't go as the controller would like them to. I never sleep any of the 11 Sandforce drives I oversee and attribute much of the stability and lack of RMA's to that precaution alone.
PS.. if you do actually sleep the drive then you'll want to change from the typically defaulted S3 sleep mode to S1(in the bios) as that's the only way to keep power to the drive. Or temp disable all sleep/hibernate modes in the W7 power options while you logoff idle the machine. That will give constant power and lower activity since W7 will shutdown many backgroud activities and allow faster recovery. A single overnight logoff idle is usually sufficient for light to moderate usage and the amount of free space left after the OS/apps/data is written should be as high as possible when the required write loads are higher than average. IOW, do a bunch of pic or video edits in a particular session?(even streaming media will buffer huge amounts of data).. then that night would be an excellent candidate for some added recovery time. So, adjust as need to the SSD's write loads.
Facebook
Twitter