Firefox acceleration tips: Modify parameters-Firefox runs faster

Article Title: Firefox acceleration tips: Modify parameters-Firefox runs faster. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Firefox acceleration tips: Modify parameters-make the smart Firefox run faster

1. network. http. pipelining

Enter network. http. pipelining in the Filter and double-click the Filter to set the value to true. The default value is false. If this key value is not found, right-click to create a Boolean and assign it to true.

As I have explained before, after activating this key value, Pipelining sends a connection request in multiples to improve the connection speed. Most websites on the network are based on the HTTP protocol, while HTTP 1.1 supports multi-threaded connection requests. This operation can reduce the time for Firefox to load webpages. However, not all Web servers support this operation, so when you modify the key value but do not see any actual effect, please do not yell at me.

2. network. http. pipelining. maxrequests

In the Filter, enter network. http. pipelining. maxrequests. Double-click and assign the value to 8. The default key value is 4.

3. network. http. proxy. pipelining

Enter network. http. proxy. pipelining in the Filter, double-click the Filter, and assign the value true.

The principles of these two optimizations are the same as above, so I will not explain them more here.

4. network. dns. disableIPv6

Enter network. dns. disableIPv6 in the Filter, double-click it, and assign the value to true.

IPv6 increases IP addresses from 32-bit to 128-bit to support larger address spaces when users send connection requests to a IPv6-capableDNS server at a terminal, the server may return an IPv4 address incorrectly. Firefox can be clear about all this, but it will inevitably lead to signal delay when debugging in Firefox, so here we assign her true to disable her.

5. content. interrupt. parsing

Right-click a new Boolean value, and the key name is content. interrupt. parsing. The value is true.

This key does not exist. After we activate this key value, when the target webpage is loaded, Firefox will interrupt the parsing process based on a certain frequency and continuously feedback the webpage information she has collected to the user, it means something like streaming media. At this time, Firefox is very smart, and it won't be able to drill the horn all the time. In the following content, I will also detail the charm of this key value.

6. content. max. tokenizing. time

Right-click to create an Integer, and the key name is content. max. tokenizing. time. The value is 2250000.

This key value is used to specify the processing cycle of a cyclic event. The unit here is microseconds. Theoretically, the smaller we get this value, the smoother the webpage will be visually loaded, because Firefox will feed back the parsed webpage information in a very short unit of time. However, this will undoubtedly delay the overall loading time of the Web page. Therefore, we may wish to increase this cycle to accelerate loading of the web page theoretically.

7. content. Contents Y. interval

Right-click to create an Integer, and the key name is content. Every y. interval. The value is 750000.

Loading a webpage is actually a great learning. Let's take a look at the slow motion. We should first call the pre-loading page, which is not very professional in the webpage information received by the terminal for the first time. This page may be incomplete pictures or text, or other media files. The time it takes from the first time we send a connection request to the remote host to the time we receive the pre-load page on the terminal is the key value we want to define here. In theory, when we set this time to a very low level, we will certainly get the so-called pre-load page faster. But this is a way to take eggs, this virtually increases the loading time of our entire page. According to the official statement, lower than 100,000 will reduce Firefox's performance. Well, let's put her down to 750000.

8. content. Contents Y. ontimer

Right-click a new Boolean value, and the key name is content. Every y. ontimer. The value is true.

In order to make the above setting take effect in 750000 microseconds, you also need to activate this key value. Only these two key values work together.

9. content. Contents Y. backoffcount

Right-click to create an Integer, and the key name is content. Policy. backoffcount. The value is 5.

This key value controls the number of times Firefox's built-in counters load the page before return to zero. We divide the target webpage into multiple parts for download. After each part is downloaded, the counter returns to zero. -1 indicates that there is no limit. If the value is 0, this function is disabled. Here we set her to 5. When the number of returned requests reaches 5, and this part of the page is not completely downloaded, the rest of the undownloaded webpage content will not be carried back at as we set out in the previous five times, but will be downloaded at one time. That is to say, in the process of downloading this part of the web page, Firefox gave us a total of 6 times of information. The first five times of time interval is the 2250000 microsecond period we set in the preceding key value, however, there is no time limit for the last 6th times. When will the rest be finished and when will the feedback be returned.

The setting takes effect only when the content. Policy. ontimer key value we mentioned above is true.

10. content. switch. threshold

Right-click to create an Integer, and the key name is content. switch. threshold. The value is 750000, that is, 3/4 seconds.

We mentioned a key value content. interrupt. parsing: by activating her, we can actually interact with Firefox during page loading. After all, our hearts are full of love. After activating content. interrupt. parsing, when the page is loaded, Firefox has two operation modes: high-frequency and low-frequency interrupt modes. When the high-frequency mode is used, the webpage feedback frequency is also very high, and the webpage loading process we see in front of the monitor will be smoother. Low-frequency webpage feedback is relatively low, but the loading time is faster. The high-frequency mode is activated when we move the mouse or touch the keyboard. After some time, we did not touch the mouse or keyboard, and the program did not receive any instructions from the mouse or keyboard, Firefox automatically enters the low-frequency mode, the so-called period of time is the value we want to specify here.

11. nglayout. initialpaint. delay

Right-click to create an Integer, and the key name is nglayout. initialpaint. delay. The value is 0.

This actually delays the display speed of the entire webpage, but users prefer to read the webpage before the entire webpage is fully captured (just like streaming media ), so here we can adjust the value to zero to accelerate the speed at which users can read the web page. Sometimes the reading speed is not proportional to the loading speed.

In the case of stable network conditions, these optimizations will indeed have some effect, not just psychological effects. When you speed up your browser, you can also refer to them a little.