In Is a 40GB SSD practical to use for ' / ' Jorge describes how he symlinks directories in his /home
that would benefit from being on an SSD. The directories he names are
~/.cache
~/.config
~/.gconf
I know how to make the symlinks. What I am asking for is if this is a good list of directories in /home
that benefits from being on an SSD? I figure that good items on such a list are files that are read often. The reason for asking this is that I cannot fit all of /home
on the SSD but I still want to get as much performance out of the SSD as possible.
Here's a list of other things that might be useful (I've made this a wiki post so anyone can add to it):
.cache
- temporty cache files for browsers and other programs..config
- config files for programs.gconfd
abd.gconf
- GNOME configuration files.gegl-0.0
– file for GIMP.gimp-2.6
– files for GIMP.gnome2
– used by some GNOME 2 applications.gvfs
– data folder for the GNOME virtual filesystem.local
– user specific data. You will lose the Nautilus Trash functionality if this directory is put on a different partition..macromedia
– files for flash.mozilla
– where all your Mozilla Firefox cache is.thumbnails
– thumbnails for pictures, videos, etc (used by Nautilus).thunderbird
– where all your Mozilla Thunderbird cache isI would put everything on the SSD, provided that it's a modern SSD (i.e. fast and doesn't suffer from poor write-leveling), and provided that everything fits.
The latency improvement is really something.
I would just have the root directory (
/
) as SSD. Keep/home
on a HDD (since in my experience, it can take -loads- of room). Also the/boot
on the SSD, if you are going to make separate partitions. That way you have the loading time benefits of SSD. That's my opinion.if you really wanted to use the SSD for home, I would put the configuration folders on there (the
/.whatever
) folders, to speed up configuration loading. It wouldn't be as fast as loading the entire program from SSD, but it's an improvement nonetheless. I don't know how to map certain elements of/home
to the SSD however, but themount
command comes to mindWhat I would advise, is have everything in one big
/
partition on the SSD (including your home directories), and then, if the SSD is not big enough for all your large files, mount your HDD separately as, say,/media/BigHDD
or whatever, and put your large files there.That way, all your dotfiles (files and directories beginning with a dot in your home directory) will be on the SSD, including new ones that software might create. It is often these dotfiles (particularly
.cache
) that are frequently read and written to and therefore would benefit from SSD the most. But that isn't to say other files and directories wouldn't also benefit.If your SSD space is not particularly limited, there is no reason to keep anything off of it. Have everything on it. Then, if you need to store lots of large files, such as for video editing, photography, your music collection, etc and these don't fit on there, then have a separately mounted drive for these.
I used to use an Asus EeePC 900. That thing had a 4GB primary SSD. That is limited space, requiring careful partitioning. A 40GB SSD is not limited.
If I had to write a list of what things would most benefit from being on an SSD I'd put them in this order.
~/.cache
- the cache area of your home directory, where software like browsers keep their cache./usr
and/lib
- just to improve start-up time of applications, and boot time./etc
- some software needs to read a lot of files in here when it starts./tmp
- some software uses this for temporary storage, but less so for user software./var
- system software sometimes stores temporary or frequently changing files here.~/.config
- config files for your user software and account.As you can see, it's somewhat spread out over the drive.
It may be more useful to see a list of what doesn't benefit so much from being on an SSD:
Media files, like music and videos.
Any other large documents, like the original images if you do photography.
Backups or large archives (eg, of other systems)