Difference between revisions of "Speeding Up Firefox"
m |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ''To readers from outside of Digibase Employees: This is just a working, terse form document, it's not a complete document as of yet, you may attempt to utilize content but it is at your own risk.'' | + | ''To readers from outside of Digibase Employees: This is just a working, terse form document, it's not a complete, stable research document as of yet, you may attempt to utilize content but it is at your own risk. Variables in this document of paths that you must adapt to your system are denoted as <span style='color:blue'>$variable</span>.'' |
| Line 10: | Line 10: | ||
The location of the cache that may be relocated is: | The location of the cache that may be relocated is: | ||
| − | * /home/''username''/.mozilla/firefox/''profilename''/Cache | + | * /home/''<span style='color:blue'>$username</span>''/.mozilla/firefox/''<span style='color:blue'>$profilename</span>''/Cache |
| − | ===MIME type inefficiency | + | ===MIME type inefficiency=== |
====Linux Solution==== | ====Linux Solution==== | ||
Relocate the following to tmpfs locations and create scripts to copy their contents from alternate locations into them at bootup: | Relocate the following to tmpfs locations and create scripts to copy their contents from alternate locations into them at bootup: | ||
* /usr/share/mime (tmpfs of this should be 8 MBytes minimum or higher as needed by the contents that would occupy them) | * /usr/share/mime (tmpfs of this should be 8 MBytes minimum or higher as needed by the contents that would occupy them) | ||
| − | * /home/''username''/.local/share/mime (tmpfs of this should be 1 MByte minimum or higher as needed by the contents that would occupy them) | + | * /home/''<span style='color:blue'>$username</span>''/.local/share/mime (tmpfs of this should be 1 MByte minimum or higher as needed by the contents that would occupy them) |
Alternate locations may be created at: | Alternate locations may be created at: | ||
* /usr/share/mime_permanant | * /usr/share/mime_permanant | ||
| − | * /home/''username''/.local/share/mime_permanant | + | * /home/''<span style='color:blue'>$username</span>''/.local/share/mime_permanant |
'''Note:''' the files must be available at the original locations, otherwise there may be malfunctions that may occur. | '''Note:''' the files must be available at the original locations, otherwise there may be malfunctions that may occur. | ||
Latest revision as of 03:51, 29 December 2013
To readers from outside of Digibase Employees: This is just a working, terse form document, it's not a complete, stable research document as of yet, you may attempt to utilize content but it is at your own risk. Variables in this document of paths that you must adapt to your system are denoted as $variable.
Contents
Heavy Disk I/O
Firefox seems to have heavy disk I/O issues where it may actively read/write repeatedly to disk rapidly which slows down the function of the browser and may impact other programs operating on the system.
Cache
Linux Solution
Relocating the cache to tmpfs on systems with sufficient RAM (3-4 GBytes or higher) may improve performance, about:config item browser.cache.disk.capacity should be set to a size 10 MBytes below the tmpfs size. 512 MBytes tmpfs will work on a 4 GByte RAM system. This will have a side effect of clearing cache at every system shutdown.
The location of the cache that may be relocated is:
- /home/$username/.mozilla/firefox/$profilename/Cache
MIME type inefficiency
Linux Solution
Relocate the following to tmpfs locations and create scripts to copy their contents from alternate locations into them at bootup:
- /usr/share/mime (tmpfs of this should be 8 MBytes minimum or higher as needed by the contents that would occupy them)
- /home/$username/.local/share/mime (tmpfs of this should be 1 MByte minimum or higher as needed by the contents that would occupy them)
Alternate locations may be created at:
- /usr/share/mime_permanant
- /home/$username/.local/share/mime_permanant
Note: the files must be available at the original locations, otherwise there may be malfunctions that may occur.
