I know most of the linux distros have weekly TRIM as default, but I have read somewhere that daily option would be even better. So what do you think which one is more suitable for new ssd-drives? I’m asking this because I have ordered myself a new laptop and would like to optimize it for the best possible performance.
For most desktop usage scenarios, I don’t think there is much reason to run it more than weekly.
Where are you seeing recommendations to run it daily?
OTOH, feel free to run it daily if you want to. It probably won’t hurt anything.
Unless you are doing absolutely massive amounts of deleting and writing, weekly is more than adequate.
I saw this blogpost and even if it was meant for Mint and Ubuntu users I was thinking it could be relevant for others too. I have always used weekly TRIM before so I think I will keep it that way…
That person doesn’t seem to understand what trim does…
If you have very little free space on your SSD, then running fstrim more frequently than weekly might not be a bad idea, depending upon how much over-provisioning there is vs write/delete cycles - but unless you are very low on space, that would not apply.
The Arch man page for fstrim states:
For most desktop and server systems a sufficient trimming frequency is once a week.
Free space on my SSD won’t be a problem so once a week trimming is just fine with me.
If your disk usage is not heavy, even once a month can be adequate…
This blogpost is just the opinion of one user. I would not care much about it especially because his message contradicts what basically all distros are doing.
But in many (most?) cases, once a week isn’t frequent enough: waiting an entire week before recoverable disk space becomes usable again, is simply too long.
This is a very bold statement which he does not backup with data, I would bet that you do not see a performance difference if you trim daily or weekly. Simply because you do not delete so much data per week that it would matter.
Damn, didn’t even think about TRIM when installing EOS. Is it enabled by default or do I have to enable it myself? (On Manjaro it’s enabled by default)
You can check if fstrim.timer is enabled:
systemctl status fstrim.timer
Up from the next release it will be enabled per default.
Reminds me, I haven’t enabled trim, and my system works perfectly fine. I’ll enable it next time I’m near my laptop
trim won’t cause things to not work, it impacts performance over time, especially on older drives and as the drive becomes full.
But seems everyone say that weekly trim is the best… so we should go to enable timer per default? as most common still continuous trim is used… as it is easier to enable maybe also… only needs the discard flag in fstab, where weekly need systemd timer to be enabled. I am not sure if this is even integrated in calamares
I would say, “yes”.
periodic trim is recommended over continuous by the arch wiki, the debian wiki and redhat.
Thx! And yeah, I think per timer and once a week would be fine.
calamares has no such option… as we need to detect in the very best case if TRIM is supported by a drive and afaik BTRFS does not need the TRIM timer? so needs to be detected also for some filesystems that does not work good for TRIM?
Only result is adding a warning here:
We can do that by a script on our own also, sounds not that hard to get it worked out?
Why? I would just enable it by default. The
fstrim command itself detects if a device supports trim or not. If you don’t have an SSD, it runs once per week and determines there is nothing to do.
I don’t think it should be harmful to enable fstrim timer for btrfs. Also, just because there is a btrfs filesystem on the disk that doesn’t mean there is only a btrfs filesystem.
What filesystems don’t support trim? trim occurs at a hardware level inside the controller.
Using the discard mount option has a negative impact on performance. It triggers a trim operation every time a file is deleted. Using the fstrim timer is much better.