How often and for how long does Trim Enabler need to run? As of Yosemite, DIY, or non-Apple installed SSDs have Trim support challenges using applications such as Trim Enabler. Assuming one keeps their TRIM supported SSD in Yosemite, 


what is a good strategy for using Trim Enabler periodically so there are no issues with kext-signing and potential OS update conflicts while Trim Enabler is disabled? 
Can this be worked around by periodically using Trim Enabler?
How long should Trim Enabler be run?
How often? 
If SSD usage, e.g. amount of read/written data is relevant to how long/often Trim Enabler should be run, is there a way to evaluate guidelines on light, moderate, heavy use.


An excellent feature for TE would be a scheduler to run based on need, then toggle TE off and turn kext-signing back on after a scheduled maintenance run. At least until/if Apple ever reopens kext-signing to software and hardware devs. Cheers -
What I used to do was enable TRIM, reboot, create and delete an encrypted disk image that almost filled the free space, leave my MBP idling overnight, disable TRIM, and reboot. That restored performance.

I'm not sure r/w volumes will tell you anything useful. The OS reuses erased blocks and the current controllers garbage collection is supposed to make TRIM largely irrelevant (or at least that's what I read).

I don't have that machine anymore and it seems like a lot riskier process under 10.10 so I'm not doing anything with TRIM on my Mac Mini w/ a Samsung 840 EVO.