Original-Syn
Yeah as BuzzPCSOS noted there is an open issue about it not being enabled for some people. https://github.com/getsolus/packages/issues/5374
It was enabled by default at some point and was not intentionally changed, some of my systems had it enabled others did not. So it is unclear what changed and when.
For everyone else reading along.
Please note that running fstrim too often can be detrimental to the health of the SSD. This is because TRIM is a write operation that marks freed blocks for cleanup and all writes contribute to NAND cell wear.
If you have enabled fstrim.timer as described in my original post (or it is already enabled) it will run in the background automatically once per week which is perfect. Too often is bad, not at all is bad, having it run automatically once a week should be in the goldilocks zone.
You would not normally need to run sudo fstrim -av manually if fstrim.timer is enabled. The only reason I said to run fstrim manually this time around was so the OP would get immediate feedback as to when TRIM was complete so they could test if performance returned to normal. So sudo fstrim -av is not something you should be running in general to improve performance, just make sure fstrim.timer is enabled and let it take care of itself.
