Basically yes. It isn't a big issue if you have a big enough SSD and Trim enabled. Server enterprise SSDs have usually better flash that can handle more erase cycles and also the SSDs use more spare area (area that the SSD pretends it doesn't have so there is a max of filled precentage). Consumer SSDs have little fixed spare area.
There is a limited amount of writes but the issue here is that there is a difference between writes initiated by the OS and how many the SSD has to do because garbage collection is cleaning up so much.
With small early SSDs the (60GB and smaller) and bad controllers the ratio from supposed writes to actual on flash writes was 10 and higher. Sandforce (your drive has a Sandforce controller) can push it below 1 with enough free space.
Now we have bigger SSDs and better controllers that all support Trim but the flash is also getting worse. 50nm flash had more erase cycles than 19nm. Flash is the only place were smaller and smaller actually makes it worse.
Trim simply marks data as deleted. You delete a file on the HDD. All it does it delete the pointer to the file in the address book so to speak. The HDD doesn't care about overwriting data it can do it infinitely more or less. That is why you can often easily recover data you have deleted on an HDD. The data lies around until it is overwritten. The OS without Trim treats an SSD the same. Just that SSD always writes to new blocks and still thinks it has to keep the deleted file around, because the SSD doesn't know it is deleted. Only once the OS tells the SSD to write over the specific LBAs (the pages the whole space is divided into) the SSD knows that it may write over those blocks. It will still write elsewhere and now only mark those blocks as empty. Only now the garbage collection(does sort of the same as the defragmentation you used to know form Windows but on the SSD level) knows that it can consolidate some data blocks that look too much like swiss cheese.
With Trim the SSD just has more free space to work with. Other times when a block is consolidated maybe 60% of the data in it is actually deleted. Then it rewrites all these completely useless data to different locations just because it thinks it has to. That latter part lets write amplification sky rocket.
If garbage collection doesn't defragment the drive you run into performance issues because eventually it has to free up new blocks to write data somewhere. Too much garbage collection or too aggressive garbage collection hurts the write cycles and Trim helps to make garbage collection more efficient and less necessary. Without Trim you need a big forced spare area to force the certain fixed amount of maximum fill rate.
![]()
The image is linked to an article that is old but the technical reasons for Trim haven't changed. Read the theoretical stuff (
this plus the next 2 or 3 pages) the practical numbers are definitely outdated.
