Make youre Firefox MUCH MUCH faster - Page 5

grimel · #41 06-01-2005, 01:31 AM

Shouldn't make much of a difference. Dial-up can't handle the data through put.

keikiwai · #42 06-01-2005, 02:06 AM

Holy crapola! It really seems to work. Thanks! for posting in this forum, otherwise I wouldn't have read it [img]/images/graemlins/tongue.gif[/img] We'll see if I keep the settings... All the banned from Neteller stuff seems worrisome....
Peter.

keikiwai · #43 06-01-2005, 02:19 AM

Load up about:config again and scroll down to nglayout.initialpaint.delay

Now right click on it and select reset.

Not an expert, but this seems to set everything back to default.

grimel · #44 06-01-2005, 02:37 AM

Banned from Neteller? How? Why? It isn't because of this. Neteller works just fine with these changes.

NoDamage · #45 06-01-2005, 04:47 AM

[ QUOTE ]
These settings violate the HTTP protocol, and give you a speed boost by flooding the web server with 20-something connections for every single image and page request. There's a reason that they're not the default.

These settings will not only cause many web servers to have problems, but they can also make your web browser be mistaken for a flood attack, which will make the server add your IP to an "ignore" list. Stay away from these "optimized" settings, unless you know exactly what they do and how they work.

[/ QUOTE ]Nope, what you said is incorrect. You are confusing pipelining tweaks with max connection tweaks. There is in fact absolutely nothing wrong with enabling pipelining and it is intentionally designed as part of the HTTP/1.1 spec as a method of increasing performance, and is the default mode for HTTP. As long as the HTTP server you are connecting to supports HTTP/1.1, there should be no problem with pipelining.

What you are thinking about is increasing the values of max-connections-per-server and max-persistent-connections-per-server. Increasing these beyond their default values is a violation of the HTTP specification, and also contrary to what people may think, it actually decreases performance.

To understand why, you have to understand the difference between HTTP/1.0 and HTTP/1.1. HTTP/1.0 establishes a separate TCP connection for each object that it retrieves from the HTTP server, and when the object is finished retrieving, it closes the TCP connection. This means for every object that must be downloaded, a TCP connection must be established and closed, and the exchange between the client and server looks something like this:
Code:<hr /><pre>Client Server
Establish TCP connection ->
<- TCP connection established
HTTP - Request first object ->
<- HTTP - Send first object
<- TCP connection closed
Establish TCP connection ->
<- TCP connection established
HTTP - Request second object ->
<- HTTP - Send second object
<- TCP connection closed
Establish TCP connection ->
<- TCP connection established
HTTP - Request third object ->
<- HTTP - Send third object
<- TCP connection closed</pre><hr />Clearly this decreases performance because each object incurs extra TCP overhead in establishing and closing the connection for each object.

On the other hand, HTTP/1.1 supports both persistent connections and pipelining, which are meant to increase performance. With persistent connections, only one TCP connection is established for the HTTP session, and it is not closed until all of the objects are done retrieving. This removes the overhead of establishing and closing a TCP connection for each object, but is still not ideal:
Code:<hr /><pre>
Client Server
Establish TCP connection ->
<- TCP connection established
HTTP - Request first object ->
<- HTTP - Send first object
HTTP - Request second object ->
<- HTTP - Send second object
HTTP - Request third object ->
<- HTTP - Send third object
<- TCP connection closed
</pre><hr />Under this scheme, the HTTP server needs to finish sending one object before the client can request the next object, so there is some additional delay between the time that the HTTP server finishes sending the first object and when it receives the request for the second object.

Finally, with persistent connections and pipelining, the session is optimized even more, because the client can send multiple requests at once (pipelining them), without waiting for the server to send each object back first:
Code:<hr /><pre>
Client Server
Establish TCP connection ->
<- TCP connection established
HTTP - Request first object ->
<- HTTP - Send first object
HTTP - Request second object ->
HTTP - Request third object ->
<- HTTP - Send second object
<- HTTP - Send third object
<- TCP connection closed
</pre><hr />In this scenario one round trip is necessary to retrieve the first object (the HTML file) so the client can figure out what additional objects need to be retrieved, but after that all of the objects can be requested in parallel.

By increasing your number of max connections beyond the default values, you are effectively going back to the HTTP/1.0 scheme of doing things, while the entire purpose of HTTP/1.1 was to come up with a better method of transferring the files that would offer better performance. Additionally, by opening up so many connections, you may end up flooding the web server and increasing the load on it, as well as the extra traffic you generate from opening all of these connections. And indeed, some HTTP servers will drop and ignore additional HTTP connections from the same source or possible even ban your IP for flooding them.

In conclusion, the pipelining tweaks discussed in the first post are perfectly fine, but don't you dare adjust your max-connections!

For more information see here:
http://www.mozilla.org/projects/netl...ining-faq.html

axioma · #46 06-01-2005, 06:16 AM

[ QUOTE ]
I made these changes and have no problem with NEteller.

[/ QUOTE ]

Allinlife · #47 06-01-2005, 09:48 AM

crazy. thanks

CrazyN8 · #48 06-01-2005, 10:33 AM

there is also an extension that is much easier to run and adjust. I think it does pretty much the same thing....

http://www.bitstorm.org/extensions/

Jim Kuhn · #49 07-17-2005, 06:29 PM

This is amazing how fast FireFox loads!

Thank you,

Jim Kuhn
Catfish4u
[img]/images/graemlins/spade.gif[/img] [img]/images/graemlins/diamond.gif[/img] [img]/images/graemlins/club.gif[/img] [img]/images/graemlins/heart.gif[/img]

popniklas · #50 07-17-2005, 07:04 PM

Umm.. this is wierd. After making the changes I cannot acces NETeller. However, I CAN acces Gmail, which I could NOT do with Firefox prior to these changes... very confusing.

Anyway, thanks for the info, it is much faster now. (And I do have Internet Explorer for access to NETeller.)