Quote:
Originally Posted by MaDalton
Stuart, you ever heard of the problem that a website takes ages to open in Firefox but once it's loaded works fine? I am talking about 2-3 minutes for the first load
|
Yeah, ultimately that comes down to a bunch of things, including making the initial handshake (connection) and how many 'pipes' it has gathering the info and even the paint (draw) speed of the browser.... where as each load afterwards only has to do a few of those things since a lot of the info is already in the cache.
All of these things can be managed though using various settings in the about
:config.
All Firefox users should have these settings like this:
network.http.pipelining: true
network.http.proxy.pipelining: true
network.http.pipelining.maxrequests: 8
content.notify.backoffcount: 5
plugin.expose_full_path: true
ui.submenuDelay: 0
If you have: Fast Computer, Fast Connection
content.interrupt.parsing: true
content.max.tokenizing.time: 2250000
content.notify.interval: 750000
content.notify.ontimer: true
content.switch.threshold: 750000
nglayout.initialpaint.delay: 0
network.http.max-connections: 48
network.http.max-connections-per-server: 16
network.http.max-persistent-connections-per-proxy: 16
network.http.max-persistent-connections-per-server: 8
browser.cache.memory.capacity: 65536
A couple settings of note - Firefox is allocated 4096 KB of memory by default and in this configuration we give it roughly 65MB as denoted by the last line. This can be changed according to what is used.
If you have: Fast Computer, Slower Connection
content.max.tokenizing.time: 2250000
content.notify.interval: 750000
content.notify.ontimer: true
content.switch.threshold: 750000
network.http.max-connections: 48
network.http.max-connections-per-server: 16
network.http.max-persistent-connections-per-proxy: 16
network.http.max-persistent-connections-per-server: 8
nglayout.initialpaint.delay: 0
browser.cache.memory.capacity: 65536
If you have: Fast Computer, Slow Connection
browser.xul.error_pages.enabled: true
content.interrupt.parsing: true
content.max.tokenizing.time: 3000000
content.maxtextrun: 8191
content.notify.interval: 750000
content.notify.ontimer: true
content.switch.threshold: 750000
network.http.max-connections: 32
network.http.max-connections-per-server: 8
network.http.max-persistent-connections-per-proxy: 8
network.http.max-persistent-connections-per-server: 4
nglayout.initialpaint.delay: 0
browser.cache.memory.capacity: 65536
If you have: Slow Computer, Fast Connection
content.max.tokenizing.time: 3000000
content.notify.backoffcount: 5
content.notify.interval: 1000000
content.notify.ontimer: true
content.switch.threshold: 1000000
content.maxtextrun: 4095
nglayout.initialpaint.delay: 1000
network.http.max-connections: 48
network.http.max-connections-per-server: 16
network.http.max-persistent-connections-per-proxy: 16
network.http.max-persistent-connections-per-server: 8
dom.disable_window_status_change: true
If you have: Slow Computer, Slow Connection
content.max.tokenizing.time: 2250000
content.notify.interval: 750000
content.notify.ontimer: true
content.switch.threshold: 750000
nglayout.initialpaint.delay: 750
network.http.max-connections: 32
network.http.max-connections-per-server: 8
network.http.max-persistent-connections-per-proxy: 8
network.http.max-persistent-connections-per-server: 4
dom.disable_window_status_change: true
Give that a try based on your setup, and you should see an improvement.
It won't "fix" the problem as the first time you load a site, it has to do a bunch of things using all this stuff.... and each load after will just load it from your cache.