Jump to content

speed up firefox


chin808
 Share

Recommended Posts

  • Replies 59
  • Created
  • Last Reply

Top Posters In This Topic

I too have tried it and it really does work.

I could not find the last one of the recommended lines to alter but the rest I was able to set and the one which had the 100 setting I made to 200 and it all works aok.

Firefox certainly is a great browser. I thought Galeon was great too but this one even beats it.

 

Cheers. John.

Link to comment
Share on other sites

yes, I was a galeon only person til it went gtk2 and had it's rendering probs that I believe are now fixed. I went opera...can't stand mozilla and like epiphany except it's horrid bkmrks. Finally....we have..

...oh, and thunderbird

Edited by bvc
Link to comment
Share on other sites

Ok, it works. It's about 1.5 faster on my PC (firefox 9 on Windows)

 

 

But I have to ask: what's the catch? :juggle:

 

Darkelve

Basically, with 100 open connections per web site, you're blocking out other users. Say, if a server allows only 500 connections at a time and 5 people with such a config show up, it will become slower for the rest.

 

93,

-Sascha.rb

Link to comment
Share on other sites

Both of these options are listed here:

http://texturizer.net/firefox/tips.html#oth_pipelining

 

Set the value of network.http.pipelining to "true".

Set the value of network.http.pipelining.maxrequests to "100".

Set the value of network.http.proxy.pipelining to "true"

Pipelining is an experimental feature, designed to improve page-load performance, that is unfortunately not well supported by some web servers and proxies.
Set the value of nglayout.initialpaint.delay to "0"
By default, Firefox doesn't try to render a web page for 250 milliseconds, because it's waiting for data. If you add the code below to your user.js file, Firefox immediately tries to render the page, even without complete data. The drawback is on slower machines where doing a "reflow" may actually cause the total page load time to be longer.

I added the last option as it was suggested and it too does make quite a big difference. Firefox is much much faster

 

iphitus

Link to comment
Share on other sites

Basically, with 100 open connections per web site, you're blocking out other users. Say, if a server allows only 500 connections at a time and 5 people with such a config show up, it will become slower for the rest.

 

But seeing as though the maximum value that firefox will accept is 8, I wouldn't worry too much. A user set value of 100 will be interpreted as 8 by the program. Besides, the problem you describe is much more relevant to the option network.http.max-connections-per-server, please don't fiddle with that value! Pipelining bascially just requests several objects at once, without waiting for a response first - which is why a dramatic improvement can be seen even with quick net connections.

Link to comment
Share on other sites

Ah, damn. You're right, Qchem--I overread the pipeline in that line of code. :D

 

Another thing to keep in mind if going for speed on firefox: only enable those extensions you really need. Depending on the Firefox build, your extensions, and your system, the more extensions -> the slower it may get.

 

So if you hardly ever use mouse gestures, don't install the extension or at least turn it off. You get the idea.

 

93,

-Sascha.rb

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...