OT - Firefox tweaks

Make that 'die-hard': Spell checkers will knot correct sin tax airs.

--
Luhan Monat: luhanis(at)yahoo(dot)com
http://members.cox.net/berniekm
"Any sufficiently advanced magick is
indistinguishable from technology."

--

    Boris Mohar

Wow! loads pages much faster. Loads faster than Opera !

Impressive Those Firefox people wrote software that the user can tweak?

nah, never catch on, Microsoft would have done it/patented it years ago

martin

"Wales is a big welsh-shaped rain collection device"

aka

Tweak Network does this for you much more cleanly.

In summary, the recommended changes in about:config are:

1) "network.http.pipelining" should be true. 2) "network.http.proxy.pipelining" should be true. 3) change "network.http.pipelining.maxrequests" to 30. Now restart your browser.

I'm just trying these myself now, but could someone summarise the potential *downsides* please? IOW, why are these not defaults, if they deliver significantly better performance?

--
Terry Pinnell
Hobbyist, West Sussex, UK

The page says it'll be problematic on slow connections. It is possible that web page designers set things up so that the text is downloaded before the pictures, so if you are on a 56k modem, you'll see the text first. Doing this will config change will mean that everything will be requested simultaneously, so you may not see the text first. This will make it seem slower, rather than faster. I'm guessing the firefox guys are assuming more modem users than broadband users.

On fast connections, requesting everything in parallel is better.

--
Regards,
  Bob Monsen

You haven't heard about the Windows hack? Set BUGS=OFF in the registry.

--
Paul Hovnanian     mailto:Paul@Hovnanian.com
------------------------------------------------------------------
Incorrigible punster -- Do not incorrige.

I set 'BUGS=OFF' but now the machine reports OSX and the other mouse button is dead. What's that all about? GG

It's much slower with my 28.8 modem.

Paul C

On an ADSL connection the improvement is great!

Ken

-- -john wide-open at throttle dot info

~~~~~~~~ Maybe I should ask Radio Shack. They claim they've got answers; but frankly, if Radio Shack were our provider, we'd _really_ be in trouble now, wouldn't we? ~~~~~~~~

It's a balance of latency (specifically for the connection establishment packets) vs bandwidth. HTTP keep-alive re-uses the same connection when more than one request is made to a server, and pipelining allows the subsequent requests to be sent before the first response has been received. Beware though, because many proxies won't pipeline (though most will now keep-alive). Speaking as someone who's implemented both.

Clifford Heath.

Correction. Connection establishment latency is the factor to consider when tweaking the total number of parallel connections, which is network.http.max-connections. I was thinking of the request latency.