Make sure you enable "trim" or other SSD mount options (for your chosen FS) on the SSD in /etc/fstab.
Swap is tough on an SSD. It hastens the "write amplification" (and thus controller's substitution of cells) in the SSD.
Another good idea is to leave "some" (say 10-15%) of the SSD unallocated in your partition scheme. Seems to improve performance (via allowing the SSD controller to re-allocate more easily).
Been running an SSD as the OS drive. some good hints in here:https://forum.sabayon.org/viewtopic.php?f=57&t=26323
I found btrfs (and recent major security holes reaffirm this) a massive annoyance on the SSD. Chose your favorite filesystem, I personally like XFS, it had the least amount of base code mods to decently support SSDs. The toolset is darned good.
Still no clue why /boot is a separate partition other than lazy habits of anaconda authors, it was so when floppies were used to boot kernels in 1993 if a bad kernel build didn't work......
I've been doing in-kernel programming for 20+ years, and running linux massive server farms without a boot partition for 10 years and can't find anyone to explain why:-) Humor intended!!
my /etc/fstab entry for SSD looks like:
- Code: Select all
UUID=485dd59f-9831-4055-9184-18031eb6aa33 / xfs ssd,discard,noatime,nodiratime 0 0
note that "discard" enables TRIM support, and "noatime,nodiratime" eliminate touch/write updates of files being opened, reducing both the number of writes, and increasing speed and longetivity of the SSD.