Optimization with High Speed
Use this trick if you are on broadband ( ADSL , cable or specialized link).
In Mozilla Firefox , type about:config in the address bar.
Read and accept the warning.
- To locate a value, just type the name or part of its name in the search field called “Filter”.
- To create value, we must right-click on the page and select “New”.
network.http.max-connections: Turn 40 (instead of 24).
network.http.max-connections-per-server: put 8.
network.http.pipelining: set to true (instead of false).
network.http.pipelining.maxrequests: Turn 32 (instead of 4).
network.http.proxy.pipelining: set to true.
network.http.max-persistent-connections-per-proxy: Put 16.
network.http.max-persistent-connections-per-server: Put 16.
network.dns.disableIPv6: set to true.
Create a new “Boolean” named config.trim_on_minimize and set the value to “true”.
This should improve the following performance:
- More simultaneous connections,
- Less return reusing existing TCP connections to send multiple HTTP requests (pipelining).
If your computer has a less powerful processor
It is possible to lighten its load by asking Firefox to wait a bit before trying to display a page if it has not received all the content.
(This is useful, for example, a Pentium 500 MHz with less than several open tabs.)
Note: This setting can also be appreciated on the powerful machines.
For it :
- 1) Enter the following command in the address bar: about:config
- 2) Make a right click, New> Numeric value
- Enter the following name nglayout.initialpaint.delay
- Enter the following value in 2000
This is the time Firefox will wait before making a first-page display if it has not received all the data after a given time (in handling 2000 milliseconds, or 2 seconds). Of course, Firefox always immediately display the page if it has received the data in less than 2 seconds.
Without this setting, Firefox will make several “reports” of the page for data reception, consuming more CPU than necessary.
Unlike a tip that circulates much, it is not recommended to set this parameter to zero.
This force Firefox to render the page as he has even received nothing, wasting CPU cycles (and therefore unnecessarily slowing down your computer).
Optimize memory usage
The Fastback option allows caching the last pages visited is handy for quick flashbacks but tends to occupy a lot of memory, but beware, if you do the following manipulations, the “back” does serve a much … (but having said that the page will still remain in history!)
1) Look for the chain browser.sessionhistory.max_total_viewers
2) Put the value “0”
1) Create the browser.cache.memory.capacity chain
2) Put the value “0”
And now, restart Firefox to reflect the new settings.