How to make your firefox even faster!!

Way off-topic, and allowed! General discussions on anything and everything.

Moderator: EG Members

Post Reply
User avatar
halfnhalf
Conversation Killer
Posts: 2722
Joined: Sun Jan 23, 2005 5:21 am
Location: SoCal

How to make your firefox even faster!!

Post by halfnhalf »

ok well someone told me to do this, well has made my firefox that much fast compared to before, so if you want to speed it up....

Here's something for broadband people that will really speed
Firefox up:

1.Type "about:config" into the address bar and hit return.
Scroll down and look for the following entries:

network.http.pipelining
network.http.proxy.pipelining
network.http.pipelining.maxrequests

Normally the browser will make one request to a web page at a
time. When you enable pipelining it will make several at once,
which really speeds up page loading.

2. Alter the entries as follows:

Set "network.http.pipelining" to "true"

Set "network.http.proxy.pipelining" to "true"

Set "network.http.pipelining.maxrequests" to some number like
30. This means it will make 30 requests at once.

3. Lastly right-click anywhere and select New-> Integer. Name
it "nglayout.initialpaint.delay" and set its value to "0".
This value is the amount of time the browser waits before it
acts on information it recieves.
my firefox hasnt been screwing up, so i guess its pretty safe to do.
Image
arke
Beware my tactical spam
Posts: 482
Joined: Tue Feb 15, 2005 3:53 am
Location: ::1

Post by arke »

A friend made a post like this several months back, crossposting my reply:
Load "about:config" by typint it into Firefox's address bar. Scroll down and look for a bunch of parameters that begin with "network" and change these three:
No need to scroll. In the edit box at the top type "network.http" and it'll trim the list to about 20 entries.
Set "network.http.pipelining.maxrequests" to some number like 30
I've read that any number above eight will be reduced to eight internally.
Lastly right-click anywhere on the config page and select New-> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it recieves.
Setting it to zero milliseconds can also be bad. If set to 0, the browser will begin drawing immediately upon receiving any data. With some sites (table heavy ones and slow sites), it'll have to completely redraw the screen several times until it gets it right. However, you do get the feeling that the browser is more "responsive" and some people like that. I have mine set to 100 ms for a variety of reasons.
User avatar
Artezul
Flexing spam muscles
Posts: 568
Joined: Thu Apr 14, 2005 12:18 pm

Post by Artezul »

Good stuff.
"Don't you get it yet?! If she's beautiful, you'll die instantly!!" Chopper
User avatar
psi29a
Godo
Posts: 5387
Joined: Tue Jan 11, 2005 2:52 am
Location: The Lonely Mountain
Contact:

Post by psi29a »

Be carefull though, pipe-lining is a http 1.1 addition to the spec. While it can make response times faster, some servers just don't support 1.1 standards and will barf at you. So, if you notice anything funky happening, you might want to turn pipe-lining off.

The forums run on apache2 with 1.1 support though. :D
Post Reply