> You could put the cache directory in say /tmp via an autoconfig.cfg file
> - see:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__developer.mozilla.org_en-2DUS_Firefox_Enterprise-5Fdeployment&d=DwIFAw&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=wxFGfz8GIjhjCEFeFXdAWyev20iqcyWzbJC3cLyTJUU&s=N4vgysHxY6w7lm96csd6ms1LYRRaNaLBvoUO6Yyevu0&e=
>
> - this may help in your case - with something like:
>
> var cache_dir = "/tmp/." + getenv("LOGNAME") + "/Cache/";
> lockPref('browser.cache.disk.parent_directory', cache_dir);
Is there a difference from using your suggestion vs. what I did here:
pref("browser.cache.use_new_backend", true);
pref("browser.cache.disk.enable", false);
pref("browser.cache.memory.capacity", 204800);
I also added these purported speed enhancements in the autoconfig:
pref("browser.startup.homepage_override.mstone","ignore");
pref("network.http.pipelining.ssl", true);
pref("network.http.pipelining", true);
pref("network.http.proxy.pipelining", true);
pref("network.http.pipelining.maxrequests", "120");
pref("network.dns.disableIPv6", true);
> If your profile directory is on an NFS share, then you will probably
> want to add:
>
> lockPref("storage.nfs_filesystem", true);
I don’t see if this fixes any performance/speed issues, or does it? I see this:
…"led to Firefox functioning incorrectly, for example, navigation buttons not
working as expected, and bookmarks not saving"
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/5.11_technical_notes/known_issues-firefox
<https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/5.11_technical_notes/known_issues-firefox>_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
