Firefox Optimization

[arsonistx]

Hello, I found this quite a while ago but I don't remember where..
So I thought I would share it with x10.

Anyways, this will speed up your Firefox, and you will see much better performance.
To do this, follow the instructions:

Open your Firefox browser, and in the address bar, type in:
about:config

Now in the search bar near the top, below the address bar, type in:
network.http

Find the following lines:
network.http.pipelining
network.http.proxy.pipelining
network.http.pipelining.maxrequests

Double click on the first two (network.http.pipelining & network.http.proxy.pipelining) to make them true.
Change the value of network.http.pipelining.maxrequest to a number like 20.

This will make web pages speed up more visibly.

Now, to make the browser display everything as soon as it is loaded, add a new integer (right click anywhere > add > integer) and name it nglayout.initialpaint.delay and set the value to 0.


After all of this, restart your firefox (not sure if you have to or not, but I did) and your browser should be working much more efficiently.

Thanks for reading.

 

[QuwenQ]

This is NOT a good idea:

Yes, enabling HTTP pipelining can dramatically improve networking performance. The downside, and the reason it's not enabled by default, is that it can prevent Web pages from displaying correctly. If you've enabled this, and you find pages that aren't displaying correctly, please don't blame Firefox or the Web developer. It's probably the fact that you enabled an "unsupported" feature which is incompatible with some Web servers and proxy servers.

The second change, setting the initial paint delay at zero, may get you some content on the screen faster, but it's worth noting that it will dramatically slow down the time it takes the entire page to display. Here's what's going on. Gecko, Firefox's rendering engine, is trying to optimize between the cost of waiting for a bit more data versus doing more painting and reflows as new data comes in. Waiting a bit longer before it starts painting the page gives Gecko a chance to receive more content before chewing up CPU cycles to render and reflow the document. If you drop this value down to zero or near zero, that means you'll see the page start displaying a bit earlier, but not having received much data in that short interval, you'll have a lot more paint and reflow cycles to complete rendering of the page.

This one probably comes down to a combination of bandwidth, CPU speed, and personal preference. If it works for you, and you don't mind the side-effects, then great. Just note that what works for one person/system, may not work for another.

Yes, there are tuning change you can make (even at compile time, see Moox' optimized builds) that will dramatically alter the performance characteristics of Firefox. Feel free to experiment, but remember that most of the defaults are defaults for a reason. If your browser starts misbehaving or web sites look broken, it might be worth going back to default settings.

 

[arsonistx]

Oh wow, I did not know about this.
Thanks a lot, scratch that, not a good idea people!

Haha.
I'm switching mine back to normal.

 

[QuwenQ]

Heh. xD
PH34R MEH PWNAGE.
=)

 

[Slothie]

Yes, enabling HTTP pipelining can dramatically improve networking performance. The downside, and the reason it's not enabled by default, is that it can prevent Web pages from displaying correctly. If you've enabled this, and you find pages that aren't displaying correctly, please don't blame Firefox or the Web developer. It's probably the fact that you enabled an "unsupported" feature which is incompatible with some Web servers and proxy servers.

Never happened to me yet

 

[arsonistx]

Actually, it has happened to me quite a bit. Every time I used to visit my website, some of the images wouldn't load at all, but then I would refresh and it would be fine. Or a different image(s) wouldn't load.

I don't suggest this at all anymore, now that I figured out what was causing that to happen.

 

[alexandgruntz]

Never happened to me.

 

[user123]

thanx anyhow ^_^

 

[ares545]

Yea, i've found pipelining to hinder some web pages such as comcast.net

 

[thugboy]

you will find this on every forum

 

[gothcrow]

good

 

[malfist]

the pipelining does work, but it increases the load on a server by quiet a bit.

Also, pipelining only works if you have a fast internet connection to make the new connections quick enough that the overhead doesn't matter. Kinda a catch-22.

 

[agaitu]

i has enabled pipelining through tune up utilities it has increased performance a little but some times firefox doesnt open any pages there might be some problem