Great -- yes, it all should work that way! Here's my coolest tip for SSD tweaking:
Eliminate many SSD writes by setting your browser cache in /run/shm (i.e. in memory). (Not a bad security enhancement, either, to have the cache go "poof" after each reboot!). For example, in the Firefox/Iceweasel address bar we enter "about:config" and confirm the warning. Now right-click in the white space and choose "New ==> String" and we create a new entry called:
After double-clicking the new string, we assign it the value:
Now as user in the terminal create a directory:
After a Firefox restart, browser caching happens in memory, not on the SSD.
For chromium-browser, the cache location is set with the “--disk-cache-dir=”DIRNAME” launch command option. So to outsource the chromium-browser cache:
Open the chromium-browser launch icon for editing, change to the “Application” tab, and edit the start command to read as follows:
/usr/bin/chromium --disk-cache-dir=/run/shm/chromium-cache %U
The new browser cache directory in /run/shm will not survive a reboot. To automate this process, put the following “auto_browser_cache.sh” script in your ~/.kde/Autostart folder (for KDE users, or the autostart folder in Gnome/Unity), and then “chmod +x” to make it executable:
mkdir "$NEWDIR" &
mkdir "$NEWDIR1" &
mkdir "$NEWDIR2" &
Analogous cache outsourcing configuration can be made for other browsers, if they allow the user to specify the cache location, and the startup script can be adapted to add directories for each browser that the user wants to run.
NOTE: For a desktop system that remains booted for long periods, and depending on the memory capacity and browsing activities, the outsourced browsing cache could grow to a problematic size and need to be manually cleared to avoid sending the system into swapping.