Leaderboard

should be a patch under KextToPatch. Otherwise it can be done in the terminal Check in system information under Sata/Sata express to verify if Trim is enabled or not sudo trimforce enable sudo trimforce disable

Annoying... When running OS X on an Intel Series 330 SATA-III (6Gb/s) SSD, boot time is dramatically impacted if the IOAHCIBlockStorage kext is binary patched to enable TRIM support (binmod of IOAHCIBlockStorage to replace hex string 00 41 50 50 4C 45 20 53 53 44 00 (="APPLE SSD") by a string of 00s). I've made some comparisons with my Dell Latitude E6440: 1) Vanilla kext - No TRIM support: . boot time Mavericks 10.9.5 (13F1077): ~7s . boot time Yosemite 10.10.3 (14D136): ~8s 2) bin-patched kext - TRIM support: . boot time Mavericks 10.9.5 (13F1077): ~46s . boot time Yosemite 10.10.3 (14D136): ~50s I had previously read similar reports but I'm still a bit baffled as I do not experience such slowdowns on my D630 (ICH8M controller, SATA-II 3Gb/s) fitted with a SATA-III (6Gb/s) 128Go SAMSUNG PM830 + TRIM enabled. Will need to try a swap out to try and verify if it could be controller related or SSD related.

Having replaced the Intel SSD by a 256Go Samsung SM841N mSATA SSD, I can report that the issue lies with the Intel drive itself. Slow boots cannot be reproduced neither with the Samsung mSATA SSD, nor with the Samsung PM830 SSD whether fitted to my SATA-II Latitude D630 or my SATA-III Latitude E6220. However, slow boots are reproduced with the Intel SSD when fitted to the D630 and the E6220.