On 04/07/2018 03:28 AM, David C. Rankin wrote:
On 04/07/2018 05:04 AM, Knurpht @ openSUSE wrote:
Leave it up to the system. I've been using SSD's for years now, and I treat them no different than I treat HDDs, and trust the system to know how to optimally set things where needed.
That's what I finally decided. I found fstrim.timer enabled and giving me a weekly trim. That's good enough for me. Thanks for the feedback.
There are threads in the list archive about this very subject, posted by myself and others. Some of these cited articled by Ted Tso. Summary: Get rid of any discard settings in fstab, use systemd fstrim.timer, as you've decided already. The next generation of SSDs probably will work just fine with discard only. But current ones work better with fstrim scheduled. After massive deletes, running an extra trim manually afterwards doesn't hurt. I just did an upgrade and running an fstrim -a gets pretty busy for a while. Trimming once a week is optimal for most user's machines. Over provision your partitions. Sizing too precisely doesn't allow the drive to do wear leveling. Some recommend leaving some un-allocated space, but that's nonsense and you can just add that extra space to / or to /home if you have one, and you will get the same wear leveling functionality. As for noatime, relatime argument, keeping atimes makes sense if you can name even ONE single valid current use for atimes. If not, turn it all off and save your SSD with noatime. The BTRFS people said that BTRFS is not optimized for use with SSDs, I don't know if that has changed, but I've still got BTRFS on my 5 year ban list. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org