[quote=lopark]I used the full Mozilla client for a while, then switched to Firefox about a year or so ago. I love it. Best browser, period (though to be fair, I haven't used Apple's Safari yet.)
BTW, here's a little trick to speed it up a bit. Enjoy :)
[quote]
basically after getting to the hidden config settings you set the browser to request more data that it usually does.
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.
- 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.
- 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 receives.
If you?re using a broadband connection you?ll load pages MUCH faster now!
[/quote][/quote]
Actually, don't do that. The pipelining is good, I'll give you that. However, maxrequests going up is bad bad bad. What that does is hammer servers badly with a ton of requests. I'm just going to paste this from another board I'm on, as I feel this explains the maxconnections problem fairly well:
EDIT: D'oh, I'm a moron. maxrequests, not maxrequests-per-server. Nevermind. Maxrequests going up is fine as long as per-server is left as is. I'm a dumbass, but I leave the information here for others who might not know.
[quote]Connection Tweaks
The "other" type of optimization commonly seen instructs you to alter the "network.http.max-persistent-connections-per-server", "network.http.max-connections-per-server" and other related settings. These are EXTREMELY DAMAGING "optimizations" to apply and should be avoided at all costs. These settings violate the HTTP protocol, which recommends a limit of 2 connections per server. When you increase it beyond that, a lot of bad things begin to happen:
The web server is often the hardest hit. The Apache web server maintains a number of "slots" which are processes lying around to handle requests as they come in. Since they usually come in at a steady rate, the server can create and destroy extra processes as needed to handle the load. When you and your "optimized" settings hit the server however, almost all of the slots that are idle are suddenly taken up by your browser. This forces the server to suddenly create a bunch of new processes to handle other traffic which is a CPU-intensive task. When you are done hogging up the slots, the server suddenly finds itself with way more processes than are needed for normal traffic, so it will kill off the extra ones.
What's worse is that since most tweaks involve such a high number of connections, once one element has been transferred, the connection is never used again. This forces the web server to hold all the connections in "keepalive" state as under normal circumstances, more than one request is sent per connection. TCP never gets a chance to automatically find the best RWIN for greatest speeds, load on routers between you and the server is increased thanks to all the extra packets... the whole basis of the HTTP/1.1 specification was to get away from the "one connection per element" days of HTTP/1.0, by applying these tweaks you are simply going back to the 1.0 days.
It's also worth pointing out that there exists an Apache module and netfilter settings that could cause your additional connections to be blocked from the server, resulting in very slow page load times, broken images and possibly even a complete IP ban for this "flooding" behaviour. Please, stick with pipelining and do not touch these settings. There is a very good reason why they are not the default.
If you have read and understood this entry thoroughly, you will notice that enabling pipelining will give you HIGHER performance than increasing the maximum number of connections! This is because with pipelining, even though there are only 2 connections to the target web server, you are still sending all your requests at once. Since you are re-using the same connection, TCP has a chance to tune the Receive Window, keep-alive is made useful and everyone is happy.[/quote]
Intialpaint at 0 is good, as is turning on pipelining. However, turning up maxrequests(EDIT: My bad. maxrequests-per-server, not just maxrequests) is bad bad bad bad bad. It might be faster for you, but it puts other people's resources under severe strain. Don't do it.
Firefox is great, yes. The extensions make it just an incredible browser, and I only keep IE around for a small handful of sites which won't work without it(otherwise, IE would be blocked from ever running again on my machine).