Couple of interesting articles on SSD optimizing & performance

FWIW, I'm sticking with sysrestore on, even though my boot is an SSD.
 
It saved my butt yesterday. Somehow, I don't know if it was Chrome or Microsoft Edge, but a malware Trojan got in - disabled Window Defender, and proceeded to change search settings, weird things things show in the task tray, and so on. I brought up sysinternals process explorer..after about a minute a I tired of playing wack-a-mole trying to kill all the recurring processes. I pulled the plug on my internet connection. I went through and removed a few startup entries, and so on. Still, It bothered me that somehow the Trojan disabled Windows Defender by applying some sort of a group policy to it. Luckily, I had a good restore point from the day before.

It's not that I can't reset my PC and reinstall all my software - all my license data and serials are is stored in multiple cloud accounts plus the software vendors themselves - it's just that it's an all damn day experience installing gigabytes of software....
 
System restore saved my bacon - so I've decide that the wear and tear on the SSD is worth it.
 
My project directories, temp directories and such are symbolic links to directories an a spinning-platter hard drive - that's where most of a disk drive's wear and tear comes from, anyway.
 

Beware, most of those tips are 4-5 years old and many are probably obsolete by now.

>it gets reset by Windows
Can't say I ever had that issue.
 
With SSD drives - if the PC has adequate RAM I'll usually set the page file size at a static 1GB or variable 200MB to 1GB for logging Crash Dumps*.  Windows will warn you it needs at least 800GB for crash dump storage if you try to set it lower or eliminate it.
 
*That being said I've haven't bothered trying to decipher a BS dump in years. When my system blue screens its usually due to swapping audio drivers back & forth. So maybe it's more efficient to completely turn off and only switch it on if you're experiencing crashes.