FIREFOX ON SPEED: Firefox Speed Tweak

Page 7 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Insomniak

Banned
Sep 11, 2003
4,836
0
0
Wow. I thought firefox was fast already, but this thing turns on the burn. It'll probably spike server bandwidth like crazy using the multiple connection method, but it's worth it.
 

Medea

Golden Member
Dec 5, 2000
1,606
0
0
Originally posted by: Jeff7
Originally posted by: fs123
There is already a extension that does this and actually has a gui that lets you go in and tweak it out. Its simply called "tweak network 1.0" and you can find it here and here is a

screen shot

That one doesn't install for me. It gives an error saying that it only works on Firefox versions 0.9 to 1.0. Odd, since I have 0.93, and based on my math, that does come between 0.9 and 1.0. :confused:


Jeff -

Strange because I loaded the patch and I only had the 0.8 version and everything worked okay.

After I read your post, I updated it to ver. 1.0. I thought I'd have to re-install the patch, but when I clicked the .exe file, I got a prompt to click the "undo patch" and it will be uninstalled, so it's still installed.

Just a suggestion, but why don't you update it to ver. 1.0, not just for the patch but for the improvements as well? Can't hurt, and you should notice a difference in quicker page loads after you've added the patch.

M.
 

Rayden

Senior member
Jun 25, 2001
790
2
0
Is there any way to test this? I can't say i've noticed a difference.

Is it mostly noticeable on webpages? With pictures? Downloading large files?
 

CTho9305

Elite Member
Jul 26, 2000
9,214
1
81
Originally posted by: Rayden
Is there any way to test this? I can't say i've noticed a difference.

Is it mostly noticeable on webpages? With pictures? Downloading large files?

If you already had http pipelining on, you'll be hard-pressed to see the difference. On my connection, turning pipelining off is noticeably slower than on with a depth of 4 (the default), but anything higher has no effect I can see. Note that Mozilla is smart enough to cap the depth to 8 to prevent lunatics from killing servers in their efforts to use l33t tw34ks, so setting it above 8 doesn't change anything.
 

All this does is set the three prefs already listed. You can do this from "about:config" without the download. He sets network.http.pipelining.maxrequests to 100 which is ridiculous. I would do 16, maybe 32 max. If everyone ran his patch every server would get DOS'd like mad. No modern webserver is going to give you more than four connections anyway.
 

imported_jb

Member
Sep 10, 2004
171
0
0
i think it was mentioned once in this thread, but it didn't seem noticed, IIRC.
the other good speed tweak is:

goto: about:config
and change: nglayout.initialpaint.delay

what this does is change the delay between recieving data and displaying it. defualt is 250 (ms). you might like it.
 

Originally posted by: jb
i think it was mentioned once in this thread, but it didn't seem noticed, IIRC.
the other good speed tweak is:

goto: about:config
and change: nglayout.initialpaint.delay

what this does is change the delay between recieving data and displaying it. defualt is 250 (ms). you might like it.
250 is nice, 0 makes pages load quicker but ugly. 250ms lets the browser layout the page before displaying it. At 0 it will show it not layed out for a quarter second then it snaps into place. To some people it's not big deal, to people with "the eye" it's gross.