Let Windows do its job. Once per month it does a real full defrag, also on a SSD, to optimize the internal meta data.
The short answer is, yes, Windows does sometimes defragment SSDs, yes,
it's important to intelligently and appropriately defrag SSDs, and
yes, Windows is smart about how it treats your SSD.
Here is a reply from Microsoft:
Storage Optimizer will defrag an SSD once a month if volume snapshots are enabled. C'est voulu and necessary due to slow
volsnap copy on write performance on fragmented SSD volumes. It’s
also somewhat of a misconception that fragmentation is not a problem
on SSDs. If an SSD gets too fragmented vous pouvez hit maximum file
fragmentation (when the metadata can’t represent any more file
fragments) which will result in errors when you try to write/extend a
file. De plus, more file fragments means more metadata to process
while reading/writing a file, which can lead to slower performance.
As far as Retrim is concerned, this command should run on the schedule
specified in the dfrgui UI. Retrim is necessary because of the way
TRIM is processed in the système de fichierss. Due to the varying performance
of hardware responding to TRIM, TRIM is processed asynchronously by
the système de fichiers. When a file is deleted or space is otherwise freed,
the système de fichiers queues the trim request to be processed. To limit the
peek resource usage this queue may only grow to a maximum number of
trim requests. If the queue is of max size, incoming TRIM requests may
be dropped. This is okay because we will periodically come through and
do a Retrim with Storage Optimizer. The Retrim is done at a
granularity that should avoid hitting the maximum TRIM request queue
size where TRIMs are dropped.
So install Windows on the SSD and forget it. Windows will do everything on its own.
