and cross your fingers 😉Ĭheck the the activation of the TRIM feature: Sudo cp /System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage /System/Library/Extensions/IOAHCIFamily.kext/Contents/PlugIns/IOAHCIBlockStorage.kext/Contents/MacOS/IOAHCIBlockStorage.original Make a copy of the original kernel module:
TRIM ENABLER MAC
Some very talented and generous guys have found a way to modify the kernel module of MAC Lion (till 10.7.4 but not on 10.7.5)in order to enable the TRIM function for all SSDs and not only Apple ones. Therefore all non-Apple SSDs don’t get the feature.
TRIM ENABLER FOR MAC
Well here comes the bad news for MAC Lion owners … and the the good ones afterwards 🙂 The BAD NEWS:Īpple has restricted the TRIM function only to the Apple identified SSDs. This saves a lot of writing time, therefore keeps the high writing speed of SSDs up to their maximum throughout the life of the SSD. The TRIM function regularly deletes the unused space on SSDs while the CPU/IOs are not too busy. This is where the TRIM function of a system comes in play. This means with time the writing speed of SSDs starts to slow down drastically. In SSDs the technology demands that the old data be first erased before new data will be written, which slows down the writing time. With rotating hard disks, the new data is simply written in the available space without having to erase the old one before. That is where SSDs and rotating hard disks differ. When it is used again the new data will overwrite the old one. So the space that is been made available again will soon or later be used again as we would expect.
That is why sensitive information should always be overwritten by something instead of simply erased… but that is another subject. In normal hard disks when a file or directory is been erased, in fact the space used by the file or directory is simply put back on the unused space list. Did you just buy an SSD for your MAC running Lion and would like to get the best of it? A short explanation:
0 kommentar(er)
