In the course of another thread trying to track down my Standby RAM usage, I looked at my Superfetch service. Lo and behold it was enabled, something which is not supposed to happen as having Windows installed on an SSD is supposed to automatically disable it. Given modern SSD endurance is measured in hundreds of terrabytes written, it may not be as big of a deal as it used to be, but every little bit will help.
Found this article about Windows and modern SSDs: Don’t Waste Time Optimizing Your SSD, Windows Knows What Its Doing
There are a lot of guides out there about optimizing your SSD, but we don’t recommend following most of them. Some of the advice is outdated, and some of it was never necessary.
Much of the advice on “optimizing” Windows for an SSD involves reducing the amount of writes to the SSD. That’s because each cell of flash memory on the drive only has a limited number of writes before it can’t be written to anymore. Guides assert that you should try to avoid unnecessary wear on the SSD by minimizing the amount of writes.
But worries about SSD wear are overblown. Tech Report ran an 18-month-long stress test where they wrote as much data to SSDs as possible to see when they failed. Here’s what they found:
“Over the past 18 months, we’ve watched modern SSDs easily write far more data than most consumers will ever need. Errors didn’t strike the Samsung 840 Series until after 300TB of writes, and it took over 700TB to induce the first failures. The fact that the 840 Pro exceeded 2.4PB is nothing short of amazing, even if that achievement is also kind of academic.”
Even at 700TB, the lowest failure threshold, you could write 100 GB a day to the drive every single day for over 19 years before the drive failed. At 2 PB, you could write 100 GB a day to the drive every single day for over 54 years before the drive failed. It’s unlikely you’ll write that much data to the drive every single day. You’ll probably be done with the drive well before then. In fact, there’s a good chance you’ll die before your SSD dies of wear. Everything wears down, and SSDs are no exception–but they don’t wear down so quickly that we need to worry about it.
You still need to perform regular backups of your important files, as SSDs could fail for other reasons aside from wear. And for extremely heavy use–for example, database servers–an SSD might not be up to snuff. But tweaking Windows to write a bit less to the drive won’t make an appreciable difference.
Other guides advise you to reduce the amount of files you store on the SSD to save space. That’s because SSDs may slow down as you fill them up, just like any other drive–but this was more helpful when SSDs were tiny. Modern SSDs are larger and less expensive, so you shouldn’t have to disable important system functions (like hibernation) to stay within these limits.
There are some important optimizations, but Windows performs them all automatically. If you used an SSD with Windows XP or Vista, you needed to manually enable TRIM, which ensures your SSD can clean up deleted files and stay speedy. However, ever since Windows 7, Windows has automatically enabled TRIM for any drive it detects as solid-state.
The same goes for disk defragmentation. Performing a typical defragmentation operation on an SSD isn’t a good idea–even if wear isn’t a concern, attempting to move all that data around won’t speed up file access times like it will on a mechanical drive. But Windows already knows this, too: modern versions of Windows will detect that SSD and will turn off defragging. In fact, modern versions of Windows won’t even let you attempt to defragment an SSD.
On Windows 8 and 10, the “Optimize Drives” application will attempt to optimize your SSDs even further. Windows will send the “retrim” command on the schedule you configure. This forces the SSD to actually delete data that should have been deleted when TRIM commands were originally sent. Windows 8 and 10 will also perform an SSD-optimized type of defragmentation about once a month. Microsoft employee Scott Hanselman offers more details on his blog.
Windows 8 and 10 also automatically disable the SuperFetch service for speedy solid-state drives. Leave SuperFetch “on” in Windows 10 and it will automatically enable itself for slower mechanical drives and disable itself for fast SSDs. You don’t need to tweak this by hand–Windows 10 just does the right thing. Windows 7 will disable SuperFetch system-wide if you have a fast enough SSD. Either way, SuperFetch is disabled automatically.
Windows Update automatically updates your hardware drivers–whether or not you want it to–so you shouldn’t need to dig up new driver versions from your motherboard manufacturer’s website to go looking for performance improvements.
RELATED: Why Solid-State Drives Slow Down As You Fill Them Up
It’s a good idea to leave some empty space on your SSD, though even this depends on your SSD. “Overprovisioning” ensures your SSD has spare memory that isn’t made available to you, so you can’t actually fill up your SSD completely. If an SSD is sufficiently overprovisioned, it may not even be possible to slow it down by filling it up with data.
Aside from that, a lot of the other tips you’ll see just aren’t necessary:
In short: Trust Windows. When it comes to SSDs, it knows what it’s doing.
Black_ZION I am sure you are aware of all this but decided to post here for others that may not know. Which included me since I don't have a SSD installed.
If Windows had Superfetch enabled it seems to indicate your SSD is not considered to be fast enough to have it disabled according to the article I just posted.
Which is funny because a Samsung 960 Pro is about as fast as a drive can get, so I would submit it's a bug. Also, NEVER ENABLE NO GUI BOOT! It doesn't save any boot time, and it blocks you from seeing anything which happens at boot, such as a disk check, or any errors.