Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

* `/home` should be on the fast drive. You probably use a lot of programs that constantly read from or write to places like `~/.config` and `~/.cache`, interrupting your use to make you wait for the read/write to finish. This lag should be reduced if the drive is faster.
* `/var` should be on the slow drive. This has a lot of stuff that's not important and takes up space, like logs and package install caches. There's no reason to waste SSD space, or put wear on it with constantly writing these files.
* The rest of `/` can also go on the fast drive, if you have enough space left there for `/home`. This way, program files in places like `/bin/` and `/usr` will end up on the fast drive, so starting programs should be a bit faster as well.
In theory, you could have a more fine grained split, but IMO it's not worth the effort. `/home` and `/var` are usually the majority of my space usage, with the rest being much smaller. Might as well throw them on the SSD and keep it simple.
All this amounts to saving a few bucks on the drives. For example, you can buy a 1 TB SSD for $55 https://www.amazon.com/dp/B09WMP5B5N and a 1 TB HDD for $40 https://www.amazon.com/dp/B0088PUEPK and implement this sort of scheme to put some files on the SSD and some on the HDD. Or you could just pay $30 more and buy a 2 TB SSD for $125 https://www.amazon.com/dp/B07YD5F561 and put everything on it. So in the end, you're adding all the complexity, and spending all the time configuring it, to save $30, which might not be worth it. Actually, you can spend a few minutes shopping around and find a cheaper 2 TB SSD, so the difference is even less than $30. So whatever filesystem split you're using, should be very simple, because if it's too involved it becomes easier to just buy a bigger fast drive.

* `/home` should be on the fast drive. You probably use a lot of programs that constantly read from or write to places like `~/.config` and `~/.cache`, interrupting your use to make you wait for the read/write to finish. This lag should be reduced if the drive is faster.
* `/var` should be on the slow drive. This has a lot of stuff that's not important and takes up space, like logs and package install caches. There's no reason to waste SSD space, or put wear on it with constantly writing these files.
* The rest of `/` can also go on the fast drive, if you have enough space left there for `/home`. This way, program files in places like `/bin/` and `/usr` will end up on the fast drive, so starting programs should be a bit faster as well.
In theory, you could have a more fine grained split, but IMO it's not worth the effort. `/home` and `/var` are usually the majority of my space usage, with the rest being much smaller. Might as well throw them on the SSD and keep it simple.
All this amounts to saving a few bucks on the drives. For example, you can buy a 1 TB SSD for \\$55 https://www.amazon.com/dp/B09WMP5B5N and a 1 TB HDD for \$40 https://www.amazon.com/dp/B0088PUEPK and implement this sort of scheme to put some files on the SSD and some on the HDD. Or you could just pay \\$30 more and buy a 2 TB SSD for \$125 https://www.amazon.com/dp/B07YD5F561 and put everything on it. So in the end, you're adding all the complexity, and spending all the time configuring it, to save \\$30, which might not be worth it. Actually, you can spend a few minutes shopping around and find a cheaper 2 TB SSD, so the difference is even less than \$30. So whatever filesystem split you're using, should be very simple, because if it's too involved it becomes easier to just buy a bigger fast drive.

Communities

Review Suggested Edit