@Firefox users

Rento · Post by **Rento** » Mon Jan 03, 2005 5:57 am

Firefox flies into over drive

Is it a bird... is it a plane..?

By INQUIRER staff: Thursday 30 December 2004, 22:09
Tyan Tomcat i7221 Server board
ASK ANY OF FIREFOX'S avid supporters and they'll tell you it's the fastest browser around, true or not. Well, the INQ's stumbled on a little tweak that's easy to do and sends the browser into overdrive.

All you've got to do is type "about:config" into your address bar, wait for it to load, then alter the following entries: change "network.http.pipelining" to "true", "network.http.proxy.pipelining" to "true" and lastly "network.http.pipelining.maxrequests" to 30, meaning it will be able to make 30 requests at once.

Don't bother if you're one of the unlucky sods still without broadband, but if you are, then give it a shot. I've tried it out and it works like a charm. Thanks to forevergeek.com! ų

I've done it and it is definatley noticeable (cheers Elison on the CGA forums)

Freaky Fryd · Post by **Freaky Fryd** » Mon Jan 03, 2005 6:22 am

...and why does that mean my toast won't ever burn again...?

Dajuda · Post by **Dajuda** » Mon Jan 03, 2005 10:31 am

OMG this really works .. pages load instantly.

Alamais · Post by **Alamais** » Mon Jan 03, 2005 8:57 pm

Yeah, I saw a post about this last week and tried it out. It's amazing. You can also change another setting to make it "draw" the page faster.

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.

Doing all of this still has the potential of problems, but I haven't had any yet.

Ah yes, the HTTP pipelining and the paint delay trick. These are great optimizations to use but do use them with care. There is a metric ton behind the reasoning of defaulting HTTP pipelining to off as well as using a paint delay. HTTP pipelining can cause some older web servers to barf or refuse to serve the requested content. This is rare but still happens. The paint delay affects the reflow of pages when rendering them. Using too small of an delay can mess up reflow when not enough of the page is in memory when Firefox starts drawing. If pages start messing up then turn these options back to the default. Personally I have had great success with enabling HTTP pipelining and reducing the paint delay.