this post was submitted on 16 Jul 2023
22 points (100.0% liked)
Firefox
17865 readers
13 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Put the changes in a
user.js
file in your Firefox profile directory (the same one that probably already hasprefs.js
andlogins.js
).Use this format (same as about:config):
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.set
browser.cache.disk.parent_directory
to/home/<user>/.cache/firefox
note: if you use flatpak you might need to allow access to this directory
Thanks. This spurred some research and I decided to disable the disk cache entirely instead:
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.
just to complete this line of though, one could also use a ramdisk as the cache directory, that should have the same effect as the prefs.
Interesting, yes. By which you mean fiddling with
/etc/fstab
to mount atmpfs
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.
on linux, yes
Thanks, useful tips.
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.