Firefox Users? Ceck This Out!

[TymeKyller]

Hope You like it!!

Here's something for broadband people that will really speed Firefox up:

1.Type "about:config" into the address bar and hit return. 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.

[murtu52]

I remember seeing this on other boards, and TymeKiller, you missed a few, sorry:

I found this on another forum. This tweak worked great for speeding up the Firefox Browser.

If you want to increase the speed of your browsing with Firefox, follow these simple directions:

Open Firefox.

Type about:config in the adress bar.

Find these options, double click each one and change to below values:

network.http.max-connections: 48

network.http.max-connections-per-server: 24

network.http.max-persistent-connections-per-proxy: 12

network.http.max-persistent-connections-per-server: 6

network.http.pipelining: true

network.http.pipelining.maxrequests: 32

network.http.proxy.pipelining: true

Close Firefox and enjoy faster browsing. 

Courtesy of tj416 from DKnoppix.com Forums.

Also, doing this will put a lot of stress on the website you are visiting, so please take precaution that you don't down the site...

[jcl]

Also, doing this will put a lot of stress on the website you are visiting, so please take precaution that you don't down the site...

Indeed. Quoth RFC 2616 (HTTP/1.1)

Clients that use persistent connections SHOULD limit the number of simultaneous connections that they maintain to a given server. A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy. A proxy SHOULD use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines are intended to improve HTTP response times and avoid congestion.

[TymeKyller]

Hey thanks guys!! I didn't notice the other one I missed, I just seen that info on a website I stumbled on while looking for something totally different..

Thanks

[tg1911]

For those interested in tweaking Firefox:

Firefox Tuning

About:config entries

[rezinator]

WOW!!

These weaks are awsome!

[murtu52]

yes, indeed, they are awesome, but just be careful, as some sites are not meant to have such heavy loads that firefox will be giving....

[Pierce]

you also have to look at it like this, a server (dual xeon, with 1 gb of ram) can handle maybe 3000~ simulationus connections, so 30 simulatanious connections at any one time, limits the server hugely. Also i was reading on opera that most servers are "broken" and dont support pipeing, because they dont send the information in the header, so a lot of sites may not work either.

Pierce

[Matt]

Thank for the info guys.. this is cool

[goman87]

Old, yet very very cool.