Firefox 2 tip.

[Cranfield]

This is a tip I found on how to make Firefox 2 even faster and it works.

 

 

 

1. Type "about:config" into the address bar and hit enter. Scroll

down and look for the following entries:

 

network.http.pipelining

network.http.proxy.pipelining

network.http.pipelining.maxrequests

 

Normally the browser will make one request to a web page at a time.

When you enable pipelining it will make several at once, which really

speeds up page loading.

 

2. Alter the entries as follows:

 

Set "network.http.pipelining" to "true"

 

Set "network.http.proxy.pipelining" to "true"

 

Set "network.http.pipelining.maxrequests" to some number like 30. This

means it will make 30 requests at once.

 

3. Lastly right-click anywhere and select New-> Integer.

Name it "nglayout.initialpaint.delay" and set its value to "0".

This value is the amount of time the browser waits before it acts on information it recieves.

[il cacciatore]

Seemed to speed it up! Cheers!

[dazza]

it worked for me

[darebear]

i have it on my laptop.

 

i have no idea why i continue to use IE.

[hawkeye]

i have it on my laptop.

 

i have no idea why i continue to use IE.

 

 

 

Because you are a Social Reject B)

[pin]

I wouldn't set maxrequests to anything much more than 8, otherwise you run the risk of hitting webserver flood protection and you might make things slower for yourself. Unless you use an HTTP Proxy you don't need to set http.proxy setting, in fact this might upset some of the less well written ones.

 

Have a look here http://www.mozilla.org/support/firefox/tips#oth_rendering

[henry d]

Any chance of something in the English language :blink:

[pin]

All these settings do are ask firefox to make more requests for pages at once. Imagine the connection between you and PW is a single pipe down which you can ask for one thing at once, once you ask for one thing you have to wait for it to come down the pipe before asking for another thing.

 

Making these changes effectively multiples the number of pipes you have, each one can only do one thing at a time, but since you have more pipes you can ask for a different thing down each of the pipes you have. In theory you then have pages loading faster because you are using more of your connection to fetch the information.

 

If you have too many pipes you could flood the webserver with requests, some of the better configured ones will be watching out for "flooding" or too many requests at once. The more pipes you have the more chance of this happening. A webserver is designed to serve pages of content to you, some people like to break webservers and one way of doing this is to flood them with requests, if the webserver decides you are flooding it, it will deliberately limit the flow of information back to you, thus you get slower browsing.

[henry d]

Cheers bud,the "mechanics" of it I kinda understood,it was the flood protection and why people would want to deliberately do such a thing :blink:

[pin]

Depends. If I were an anti and took exception to a particular website, I could take it down if I wanted, for instance. Many reasons, not all of which make much sense.

[barrie0]

Thanks Cranners . :blink: