Results 1 to 7 of 7
Hi,
can ne 1 tell the best settings to attain max speed with mozilla.
I have heard that making appropriate settings speed up the browser.
I opened about :config and ...
- 05-05-2005 #1Just Joined!
- Join Date
- May 2005
- Location
- kanpur(India)
- Posts
- 31
speeding up mozilla
Hi,
can ne 1 tell the best settings to attain max speed with mozilla.
I have heard that making appropriate settings speed up the browser.
I opened about:config and tried many possibilities but all invain.
Ne 1 knowing the same...plz reply
TIA
madhuresh
- 05-06-2005 #2
- 05-06-2005 #3Linux Engineer
- Join Date
- Jan 2005
- Location
- Chicago (USA)
- Posts
- 1,028
1. Type "about:config" into the address bar and hit return. In the filter type "network.http."
2. Set
network.http.pipelining
and
network.http.proxy.pipelining
to true (double click on them).
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.
3. Set
network.http.pipelining.maxrequests
to something like 40.
This means it will make 40 requests at once.
4. 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.
- 05-06-2005 #4Just Joined!
- Join Date
- May 2005
- Location
- kanpur(India)
- Posts
- 31
thanks it worked
thanks... this is exactly wat i was looking for..
-madhuresh
- 05-06-2005 #5Linux Engineer
- Join Date
- Mar 2005
- Posts
- 1,431
This have nothing to do with the configuration of mozilla, but it would probably start faster if you prelinked it... And thanx for the options, a thing, I needed them
- 05-06-2005 #6
Just a quick note about pipelining...
This once came up on a game forum that I've used for years. The Admin explained exactly how pipelining works. Basically, if you set it to "40", you send 40 requests with each click.
This means that essentially simultaneously, the server is serving 40 requests. Now imagine 1000 users doing that. That's 40,000 requests, if each was to click a link simultaneously.
So while pipelining does speed things up, don't use it to excess.DISTRO=Arch
Registered Linux User #388732
- 05-06-2005 #7Linux Engineer
- Join Date
- Mar 2005
- Location
- Where my hat is
- Posts
- 765
Yeah, but most savy administrators will only allow up to around 12. It can be controlled from the server side. Pipeline is one of those things that really looks cool, but in reality, doesn't do much for your speed on most servers.
Registered Linux user #384279
Vector Linux SOHO 6 / Vector Linux 7 RC 3.4


Reply With Quote
