Tilted Forum Project Discussion Community

- Tilted Technology (https://thetfp.com/tfp/tilted-technology/)

- - Speed Up Firefox!! (https://thetfp.com/tfp/tilted-technology/80095-speed-up-firefox.html)

Speed Up Firefox!!

I applied the changes noted in this link, and noticed significant speed improvements! Folks at other forums I visit noticed the gains as well.

Enjoy! :thumbsup:

http://forevergeek.com/open_source/m...fox_faster.php

I would refer you to this thread.
http://www.tfproject.org/tfp/showthread.php?t=77672
Just use the patch for speed increases.

Also, you should check out MOOX builds of firefox. Just search Google for MOOX firefox and you'll be directed to where you need to be.

I tried mikec's link... works great so far

Quote:

Originally Posted by bendsley

I would refer you to this thread.
http://www.tfproject.org/tfp/showthread.php?t=77672
Just use the patch for speed increases.

I saw that thread. Since I'm the type who likes to see what changes are being made, I thought a new thread that detailed changes to be made was more appropriate than just applying a patch that you aren't really sure what it's doing. :cool:

Quote:

Originally Posted by mikec

Then did you see this post by ratbastid?....

Quote:

Well, from reading that thread, it sounds like his patch makes Firefox connect to the remote server multiple times--possibly as much as one connection per item to download from the server

Usually the browser opens one connection to the server, downloads the HTML file that is the page, then starts sucking down files referred to in that page--images, javascript files, stylesheets, etc. through that same connection. Evidently his patch makes Firefox download those files simultaneously rather than one at a time.

In theory, this should speed up page rendering dramatically. But there's a reason Firefox doesn't do that by default--it's pretty rude to the remote server. If every browser did this, it wouldn't take many people surfing the site to max out the server.

or by jonjon42...

Quote:

I think it's kinda rude to remote servers (I have one myself) and hope it doesn't catch on too much. It provides a headache for admins and may get you blacklisted.

I'm going to double-post this, once in this speed thread, once in the other, for those people who don't follow the links. Asa (one of the main Firefox developers) discusses why these are not the default settings in this blog post (emphasis added):

Quote:

After seeing at least a couple dozen blog posts all referencing these changes to "speed up Firefox", I thought it would be worth a little explanation.

Yes, enabling HTTP pipelining can dramatically improve networking performance. The downside, and the reason it's not enabled by default, is that it can prevent Web pages from displaying correctly. If you've enabled this, and you find pages that aren't displaying correctly, please don't blame Firefox or the Web developer. It's probably the fact that you enabled an "unsupported" feature which is incompatible with some Web servers and proxy servers.

The second change, setting the initial paint delay at zero, may get you some content on the screen faster, but it's worth noting that it will dramatically slow down the time it takes the entire page to display. Here's what's going on. Gecko, Firefox's rendering engine, is trying to optimize between the cost of waiting for a bit more data versus doing more painting and reflows as new data comes in. Waiting a bit longer before it starts painting the page gives Gecko a chance to receive more content before chewing up CPU cycles to render and reflow the document. If you drop this value down to zero or near zero, that means you'll see the page start displaying a bit earlier, but not having received much data in that short interval, you'll have a lot more paint and reflow cycles to complete rendering of the page.

This one probably comes down to a combination of bandwidth, CPU speed, and personal preference. If it works for you, and you don't mind the side-effects, then great. Just note that what works for one person/system, may not work for another.

Yes, there are tuning change you can make (even at compile time, see Moox' optimized builds) that will dramatically alter the performance characteristics of Firefox. Feel free to experiment, but remember that most of the defaults are defaults for a reason. If your browser starts misbehaving or web sites look broken, it might be worth going back to default settings.

I tried pipelining, and I couldn't use my bank's website anymore.