Chrome vs Firefox>?

johngalt said:

I actually had to ask because that is *only* what I knew it as.

Ask dmex, he should remember me asking over at the Vista x64 forums....

I'm sorry johngalt, how come you star words in your posts? To put emphasis on them? Sorry for asking if its obvious but I was just wondering . Also, is there any significance of the missing "n" on the end of your location?

Yeah, old IRC / email habit. I could boldface then but sometimes that gets lost, stars still seem to stand out more.

And the missing n was because I was an idiot when I made out my 'location' profile. Thanks for catching that - you're the first in 1400+ posts

johngalt said:

And the missing n was because I was an idiot when I made out my 'location' profile. Thanks for catching that - you're the first in 1400+ posts

lmao
i just ignored it...lol

Thanks Dave, I already had some of those settings tweaked but didn't know about the last one, good find.

Learn something new everyday. Thanks Dave.

Gary

davehc said:

Have you tried this old tweak for Firefox. Makes it run like lighteneing:
1. Type "about:config" into the address bar and hit enter. Scroll down and look for the following entries:
You will get a threatening warning here!
2. Alter the entries as follows: (by clicking the item)

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.

3. 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.

the only i think would have no difference is the http pipe as you are only able to use the max of 8

Network.http.pipelining.maxrequests - MozillaZine Knowledge Base

davehc said:

Have you tried this old tweak for Firefox. Makes it run like lighteneing:
1. Type "about:config" into the address bar and hit enter. Scroll down and look for the following entries:
You will get a threatening warning here!
2. Alter the entries as follows: (by clicking the item)

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.

3. 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.

Thanks very much Dave, will try this when I next use Firefox. :)

davehc said:

Have you tried this old tweak for Firefox. Makes it run like lighteneing:
1. Type "about:config" into the address bar and hit enter. Scroll down and look for the following entries:
You will get a threatening warning here!
2. Alter the entries as follows: (by clicking the item)

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.

3. 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.

Yeah, used those *and* a few more - however, with Vista managing memory the way it does and with me ahving such a nice connection to begin with, I abandoned these with Fx 3 when it went RTM. I honestly haven't seen much of a difference in terms of speed with Fx with and without those tweaks.

There are several more, I can dig them up from the old TEM/ AMI site if you want.

darkassain said:

the only i think would have no difference is the http pipe as you are only able to use the max of 8

Network.http.pipelining.maxrequests - MozillaZine Knowledge Base

There are some bad side effects, though, especially if you have problems with connections and / or dropped packets (IOW< wireless users need to *seriously* chekc this out for several days to see if it is worth it...)

http://www.mozilla.org/projects/netlib/http/pipelining-faq.html said:

How many requests should be pipelined?

Well, pipelining many requests can be costly if the connection closes prematurely because we would have wasted time writing requests to the network, only to have to repeat them on a new connection. Moreover, a longer pipeline can actually cause user-perceived delays if earlier requests take a long time to complete. The HTTP/1.1 spec does not provide any guidelines on the ideal number of requests to pipeline. It does, however, suggest a limit of no more than 2 keep-alive connections per server. Clearly, it depends on the application. A web browser probably doesn't want a very long pipeline for the reasons mentioned above. 2 may be an appropriate value, but this remains to be tested.
What happens if a request is canceled?

If a request is canceled, does this mean that the entire pipeline is canceled? Or, does it mean that the response for the canceled request should simply be discarded, so as not to be forced to repeat the other requests belonging to the pipeline? The answer depends on several factors, including the size of the portion of the response for the canceled request that has not been received. A naive approach may be to simply cancel the pipeline and re-issue all requests. This can only be done because the requests are idempotent. This naive approach may also make good sense since the requests being pipelined likely belong to the same load group (page) being canceled.
What happens if a connection fails?

If a connection fails or is dropped by the server partway into downloading a pipelined response, the web browser must be capable of restarting the lost requests. This case could be naively handled equivalently to the cancelation case discussed above.

davehc said:

set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.

Yeah, anything over 8 is assumed to be 8. So the highest you could configure this would be 8.

Attachment 4098

http://kb.mozillazine.org/About:config_entries