With discard=async set by default in the kernel, are there any advantages to doing periodic TRIM. I know the wiki states they can coexist, but just wondering what the advantage of doing both is, or if it makes more sense to disable fstrim.timer
I guess it depends on the equipment.
In my case, no longer with such young sata ssd disks, I have decided to disable discard=async and only use periodic TRIM. It has worked well for me for years.
And it looks like it’s not going to do me any good anyway (discard=async):
Christoph Hellwig:
FYI, discard performance differs a lot between different SSDs.
It used to be pretty horrible for most devices early on, and then a
certain hyperscaler started requiring decent performance for enterprise
drives, so many of them are good now. A lot less so for the typical
consumer drive, especially at the lower end of the spectrum.And that jut NVMe, the still shipping SATA SSDs are another different
story. Not helped by the fact that we don’t even support ranged
discards for them in Linux.
source of the quote
There is no real advantage to doing the periodic trim in addition to discard=async. However, it also doesn’t hurt anything.
I think I’m just going to turn it off and stick with async