This turned out to be a bit tricky to actively check, since it requires peeking under the hood into the file system-but this is Ars Technica, damn it, and this kind of stuff is what we do. We wanted to see if we could verify that TRIM was actively working on third-party SSDs in El Cap. One of the Macs we loaded El Cap on was an old 2007 Core 2 Duo iMac that had been upgraded with an SSD, and we enabled third-party TRIM on it with the trimforce command (introduced as a Yosemite feature in June 2015). If you’d like a whole deep-dive on not just TRIM but SSDs themselves, including a discussion of where TRIM fits into the processes by which SSDs keep themselves clean and operational, you can hit up our big SSD explainer. If you’d like more of a refresher on TRIM, you can check out our piece from April on whether or not TRIM is something you should care about. TRIM isn’t a mandatory thing, but it’s definitely nice to have. Without TRIM, the SSD has no way of knowing when the operating system deletes files, and the operating system has no way of telling the SSD (because typically, a "deletion" in a modern file system is actually just a quick write, not an actual-for-real zeroing-out of the deleted data). Further Reading Ask Ars: “My SSD does garbage collection, so I don’t need TRIM… right?”Īs a very quick refresher, TRIM is an ATA command that operating systems can cause to be issued to SSDs when files are deleted it tells the SSD that the blocks mapped to the deleted file can be marked as stale and cleaned for reuse during the next round of SSD garbage collection.
0 kommentar(er)
