Pipelining Knoppix's IceWeasel: a good idea, or not?

[utu]

.
Pipelining is turned off by default in Knoppix's IceWeasel.
I've turned mine on by entering about:config into the browser address line,
promising 'to be careful', and changing network.http.pipelining to true.

Most sites seem to come up faster this way for me.
I'm wondering what the down-side may be in actual practice.
Opera is the only major browser that has this parameter set to true by default,
according to wikipedia. http://en.wikipedia.org/wiki/HTTP_pipelining

Open to any comments, advice, warnings from those having some first-hand
experience in this area, either good or bad.

[utu]

ps

I had this posted in the wrong place before.

I note that mint not only recommends pipelining, but suggests setting maxrequests to 150.
The latter sounds a extreme to me; mine is still set to 4, the default.

Not sure, but I think the volume of entries in the yahoo spam file has increased.
No more get through to the inbox, but more to ignore.

[utu]

Apparently the number of requests, for mozilla is an integer 1 through 8.
The value of 1 means no pipelining.

http://kb.mozillazine.org/Network.ht...ng.maxrequests

[utu]

An independent view which seems reasonable to me:

http://egonitron.com/2007/05/25/the-...elining-trick/

[utu]

I find a significant improvement in IceWeasel's responsiveness with
pipelining turned on and maxrequests set to 8.

[utu]

I haven't figured how to quantify this, but after about a month my
impression is that for most sites, maxrequests=8 feels like a nice
improvement in browser responisiveness, relative to maxrequests=4.

However, for a few sites, the browser may 'choke' for several
seconds, as can be confirmed by watching the lxpanel cpu monitor.
I can't recall ever noticing this 'choking' effect at maxrequests=4.

My overall impression is that maxrequest=8 is (now) not the right number,
and intend to tweak it down some until the 'choking' isn't objectionable.