Comments on: Speed Up Firefox with Pipelining

By: Norman Fenton

Norman Fenton — Wed, 17 Jan 2007 22:54:20 +0000

How can I get rid of:
ad.yieldmanager.com

By: isoTop`s blog

isoTop`s blog — Sun, 07 Aug 2005 16:00:51 +0000

Feld Thoughts: Speed Up Firefox with Pipelining

I came accross this tweak for FireFox and multipiping its seems to making some sites faster but didn’t check how fast it making it.
Feld Thoughts: Speed Up Firefox with Pipelining
…

By: Justin Lundy

Justin Lundy — Wed, 29 Jun 2005 15:50:30 +0000

I’ve requested that these pipelining speed ups be included in future firefox releases as default settings.

By: David Brode

David Brode — Thu, 16 Jun 2005 18:10:52 +0000

I use gmail and found that this tweak improves performance noticably. That alone is worth it. Thanks, Brad!

By: Sander

Sander — Thu, 16 Jun 2005 09:59:47 +0000

Oh, and you might find this useful:

Set browser.sessionhistory.max_viewers to larger than zero, to get blazingly fast back and forward (like Opera) has in the upcoming Firefox 1.1 – albeit at the cost of memory usage. (Already available in the deer park preview.)
Still has bugs (think of restoring changes to the DOM due to scripting), so not yet enabled by default.

By: Sander

Sander — Thu, 16 Jun 2005 09:45:21 +0000

Note that several web- and proxy servers still break horribly if you try to use pipelining. If you suddenly start seeing websites render badly, that’s why. (This is also the reason this preference hasn’t been enabled by default.)

Setting maxrequests high is also a bad idea, as just a couple of people having done that and visiting at the same time can very swiftly bring a small webserver (which often have a limit like 100 concurrent requests) to its knees.

And finally paint delay set to 0 will actually make the total rendering time take longer, as there’s much more reflowing happening. Basically with this pref set, painting starts right at the moment that the first bits of data come in, so everything _seems_ snappier (especially on a really fast connection), but the cost is content moving all over the screen…

Don’t just take my word from it either, someone like Asa Dotzler says the same: http://weblogs.mozillazine.org/asa/archives/007164.html

By: Ruchit

Ruchit — Thu, 16 Jun 2005 05:05:34 +0000

Thats cool, I find firefox to be bit heavyweight application consuming lot of memory. I think this tweaking will result in better user experience.

Wondering if there are any drawback of doing this tweaking, otherwise firefox team might have this done it their default settings…anu idea?

By: The NOSE: Alfred Essa's Weblog

The NOSE: Alfred Essa's Weblog — Thu, 16 Jun 2005 03:03:07 +0000

Firefox Hack and HTTP Pipelining

Here’s a great hack (via Feld Thoughts and Subterrrain.net) to make Firefox download pages faster for broadband users. Browser requests are normally processed sequentially by the web server. HTTP pipelining allows multiple requests to be processed toge…

By: Chris Ueland

Chris Ueland — Wed, 15 Jun 2005 22:59:50 +0000

One thing I’ve been playing with is Google’s caching tool. While security is a whole other issue, the tool itself is pretty cool. It claims to have saved 45 minutes of cumulative download times.

I’m going to give the firefox piping a try as well.

–Chris

By: The NOSE: Alfred Ess

The NOSE: Alfred Ess — Wed, 15 Jun 2005 20:03:07 +0000

Firefox Hack and HTTP Pipelining

Here's a great hack (via Feld Thoughts and Subterrrain.net) to make Firefox download pages faster for broadband users. Browser requests are normally processed sequentially by the web server. HTTP pipelining allows multiple requests to be processed toge…