1. Type "about:config" in the adress field.
2. Set the value of network.http.pipelining to "true".
3. Set the value of network.http.pipelining.maxrequests to "100".
4. Set the value of network.http.proxy.pipelining to "true"
5. Set the value of nglayout.initialpaint.delay to "0"
Now watch as the loading times that already beat IE's go into overkill mode.
<BLOCKQUOTE><font size="1" face="Arial">quote:</font><HR><font face="Arial" size="3">Originally posted by De Rigueur: I didn't see the 'nglayout.initialpaint.delay' variable in my config.</font><HR></BLOCKQUOTE>
<BLOCKQUOTE><font size="1" face="Arial">quote:</font><HR><font face="Arial" size="3">Originally posted by fliptw:
<b> If its not there in about:config, its possibly something that mozilla can't use.
FireFox != Mozilla, tho you can build both from the same tarball.</b></font><HR></BLOCKQUOTE>
Actually flip, theres quite a few things that Mozilla supports in about:config that isn't there by default....such as making websites think that you're using a different browser. I've been using this tweak for the past couple of days without any ill effects.
The Things They Left Out extension also allows pipelining to be enabled via an options menu, as well as other configuration options that Mozilla has in its configuration panel but Firebird doesn't.
MD-2389 wrote:3. Set the value of network.http.pipelining.maxrequests to "100".
May cause problems -- if that's applied to how many open requests go to a server: Typical settings are "4" for 1.0 servers and "2" for 1.1 servers (RFC2068).
for some reason those settings are ALREADY set in my install of firefox. i'm prettysure i havn't manually set them since i last dumped a fresh windows install image.
maybe these settings are now automatically set by firefox as default in firefox ver1 (publicbeta).
perhaps someone else who has not manually applied these settings and has a fresh install of firefox could check it out to see if they are already set?
MD-2389 wrote:3. Set the value of network.http.pipelining.maxrequests to "100".
May cause problems -- if that's applied to how many open requests go to a server: Typical settings are "4" for 1.0 servers and "2" for 1.1 servers (RFC2068).
What kind of problems would that cause? If I wanted to be safe and leave it at default of 4, would I be seeing a theoretical speed increase of 4% of MD's settings or what?