I have some Samsung 830, 840, and 850 generation SSD drives here…on Intel and AMD platforms both.
I’m pretty familiar with their software. They give you some options on optimization, and these days I think a bunch of it has to do with how big your SSD drive is, and personal priorities.
Some of the optimizations depend on if boot-times are important to you. I.E. should various hibernation and sleep files be used. Such files can take a good bit of storage space, but will really speed up boot times.
If you’re running an OS on a smaller SSD drive, you might well want to sacrifice boot speed for more drive space. It’s all about personal priorities in that case. If your SSD is a smaller one, I think it’s very wise/important to do the recommended overprovisioning process (leaving a chunk of the drive un-partitioned for garbage collection purposes). In contrast, if you’re not running an OS from the drive, or it’s a larger drive with plenty of free space…overprovisioning isn’t as important.
@512gig, I’d say if you’ve got it pretty full…go ahead and do the overprovision process. It’ll give you headroom as it fills up with stuff. If all you’re running is the OS and a few apps, and got plenty of free space…you could wait.
Next comes things like disabling indexing and prefetch. If your SSD drive is larger…I’d say don’t worry about it…just leave it all on. If it’s a smaller drive, cutting that stuff off will reduce the number of writes to the drive and might help it last a few years longer at a very small performance cost to drive ‘reads’. If it’s a larger drive (I.E. 1tb or more) with plenty of free space…again I’d say either way is fine.
There are some extra ‘write speed’ enhancement modes offered by the Samsung software. These offer an ‘option’ to devote a percentage of memory to optimized write caches and buffers. On my windows 10 system, none of that seems to be an option for me to even try at this point (says unknown OS). If any of this can be enabled on your system, it shouldn’t hurt to give it a try to see if it works and offers a worthwhile performance boost. If you’re happy with write performance without enabling such boosts, and would rather keep the memory available for other things (like loading apps and samples), then just leave this enhanced write cacheing stuff disabled.