Then sync or backup the whole directory, excluding the "cache" subdirectories to save space.
(Pet peeve: Firefox, please use $HOME/.cache/ like every other app!)
You might try losing everything but the .json and .sqlite files. Have not checked, but that is probably enough. Only missing paths are regenerated when you launch Firefox.
Seems an easy way to avoid the SSD churn and syncing issues, since today's fast internet connections make disk caching less useful. That may be wrong but so far it seems as fast as ever.
Interesting, yes. By which you mean fiddling with /etc/fstab to mount a tmpfs partition and pointing the cache directory at that ? Any pros and cons you know about?
Anyway, after a bit of browsing I really cannot detect any performance difference since disabling caching. So seems a good deal so far. I wish Firefox had a simple on-off switch instead of needing a bunch of config tweaks to do this.
By which you mean fiddling with /etc/fstab to mount a tmpfs partition and pointing the cache directory at that?
on linux, yes
Any pros and cons you know about?
those who already have a ramdisk it might be pretty easy to use it and just change one preference
the ramdisk will remain until reboot so you can close your browser and you still retain the cache (might be useful depending on peoples workflow and sites they visit)
I wish Firefox had a simple on-off switch instead of needing a bunch of config tweaks to do this.
Done. 24 hours ago but still awaiting moderation! I didn't know about this forum. Unfortunately they are obviously snowed under by feature requests, many of them unmerged duplicates. So not expecting much, alas.