DescentBB

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.

This reply page loaded quickly!

The tweak is more geared for those blessed with broadband connects, but it definitely works for those like me stuck with dial-down.

I didn't see the 'nglayout.initialpaint.delay' variable in my config.

Yeah, I don't have it either with Mozilla 1.6, I just have..

nglayout.debug.enable_xbl_forms

&

nglayout.events.dispatchLeftClickOnly

<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>

You gotta create it.

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.

<BLOCKQUOTE><font size="1" face="Arial">quote:</font><HR><font face="Arial" size="3">Originally posted by MD-2389:
You gotta create it.</font><HR></BLOCKQUOTE>

Well, I added it. Not sure how to measure response time improvement. Subjectively, it might be a bit faster.

sweet, I forgot about the about:config command... I do see a marked improvement, thanks.

I see good improvement here to thanks MD.

holy cheezeballs. that's fast.

Fast++, especially on sites (like the fricken SimCity website) that consist of over 100 images.

Thanks.

Holy jebus, I guess it does!

nifty

thx MD.

<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.

"Set the value of nglayout.initialpaint.delay to "0""

Not a big fan of that-- it seems to remove the delay to display the page after some of the pictures have been downloaded. Prettier the other way.

nice. thanks md

edit: whoops, i necro posted. teehee

Necrokurupto!!! AHHHHHHHHHHHHHHHHHHHHH!@~!!!!!!

Is there any way to create a DOS batch file which will adjust the values and place the create the nglayout value?

That'd rock!

create a user.js file with the given values, like this:

and put them in firefox/mozilla's profile folder.

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?

roid, if you're using a profile that you've been using for a while, then you'll still have the same settings.

md the image didn't have firefox installed on it. it could be that i uninstalled it before making the image, but i doubt it.

I just tried the settings. There is definitely a noticable improvement in page load times. I'm using 1.0.

Thanks for the tip.

Lil bump for a question about this tactic.

Grendel wrote:

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?

Thanks! This pages is loading SUPAFAS!!! Oh wow!

One more question. nglayout.initialpaint.delay should be set as an integer and not a string, correct?

Mr. Perfect wrote:One more question. nglayout.initialpaint.delay should be set as an integer and not a string, correct?

Seeing as you're entering a number, yes it should be set as an integer.