It should be noted that as any Trim utility on Yosemite it is still prone to the issues mentioned in the support article above (but has it's own, updated one here).
I always used Trim Enabler. You should definitely enable it. Not having Trim is like using an SSD that is constantly 100% full. Which leads to inefficient garbage collection -> high write amplification -> lowered nand lifespan and lower performance.
- Meaning that Disk Sensei also requires the disabling of kext signing for both manual and automatic TRIM?
If so, how does it improve the TRIM-enabling procedure?
I recently released a successor to Trim Enabler called Disk Sensei, which improves the Trim-enabling procedure a lot. I recommend getting it over Trim Enabler as Trim Enabler will not be updated anymore. Disk Sensei is however currently 100% paid software, but the Trim functionality will be converted to a free feature soon, so you might want to wait for that (ETA June).
It should be noted that as any Trim utility on Yosemite it is still prone to the issues mentioned in the support article above (but has it's own, updated one here).
So the Chameleon is a free utility? Why i shouldn't use it? xD
No it is full as soon as enough every LBA has been written to just ONCE. The only way without trim to know data can be marked as deleted is if the LBAs have been overwritten or rewritten elsewhere. To the drive it looks as if all LBAs have been written to after they have been written to just once. Onle with Trim can it see empty space as empty space. This is the important distinction many people that say "no trim is fine" don't understand.This is only true when the drive actually is 100% full, or close to it. When there is plenty of free space, the lack of Trim is not a problem at all, assuming the drive has built in garbage collection. I have used many SSDs without Trim and there was no performance degradation. Just leave some unallocated space to ensure that there is room for the garbage collection to work and it will be fine.
No it is full as soon as enough every LBA has been written to just ONCE. The only way without trim to know data can be marked as deleted is if the LBAs have been overwritten or rewritten elsewhere. To the drive it looks as if all LBAs have been written to after they have been written to just once. Onle with Trim can it see empty space as empty space. This is the important distinction many people that say "no trim is fine" don't understand.
Garbage collection IS NOT a substitute for Trim. Every drive has garbage collection and garbage collection needs Trim to work efficiently.
Here is a nice article that explains the problem.
A drive still works when it is 100% filled because there is always some spare area. But that spare area has been shrunk since Trim has become standard and it really is a problem to use todays SSDs without Trim. They expect it.
@terencedriver Seriously read the article. You clearly got a knowledge gab there. Trim is a necessity for SSDs. Getting by without Trim is the thing of the past. It is not a question of special support but just a question of proper representation of data. The SSD and the OS see different things. Just read the article and you will understand where you got it wrong.
@556fmjoe and clearly the solution is to not partition a quarter of your drive to have enough spare area. 😉😉😉😉 Most people would not do that and it is really an impracticle solution that still leaves you with higher write amplification than with Trim. Shortening the life span of the nand just for stubberness or what?
All modern SSDs work well and better with Trim.
I recently released a successor to Trim Enabler called Disk Sensei, which improves the Trim-enabling procedure a lot. I recommend getting it over Trim Enabler as Trim Enabler will not be updated anymore. Disk Sensei is however currently 100% paid software, but the Trim functionality will be converted to a free feature soon, so you might want to wait for that (ETA June).
It should be noted that as any Trim utility on Yosemite it is still prone to the issues mentioned in the support article above (but has it's own, updated one here).