Author | Post | ||
Grivier |
Here's something for broadband people that will really speed Firefox up: 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. 2. 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. (Don't put higher than 30, coz some sites will think u r hammering and will ban u...) 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. If you're using a broadband connection you'll load pages MUCH faster now! Grivier |
||
18.09.2006 12:49:09 |
|
||
Y3HM3 |
it really makes it a lot faster, thanks!! |
||
18.09.2006 15:43:51 |
|
||
sniperkid |
wow serious speed!!! maybe even possible to do some programming challenges without programming |
||
18.09.2006 21:38:40 |
|
||
unstable |
Setting network.http.pipelining.maxrequests to any value greater than 8 would be rather pointless, because NS_HTTP_MAX_PIPELINED_REQUESTS = 8 (which you can find in nsHttp.h). There are alot more settings you could tweak. I got these settings from some other place, can't remember where: network.http.max-connections : 48 network.http.max-connections-per-server : 20 network.http.max-persistent-connections-per-proxy : 8 network.http.max-persistent-connections-per-server : 16 network.http.pipelining : true network.http.pipelining.firstrequest : true network.http.pipelining.maxrequests : 8 network.http.proxy.pipelining : true nglayout.initialpaint.delay : 0 plugin.expose_full_path : true ui.submenuDelay : 0 browser.cache.memory.capacity : 65536 (means 64MB) browser.cache.disk_cache_ssl : true // ATTENTION!!! browser.xul.error_pages.enabled : true content.interrupt.parsing : true content.notify.backoffcount : 5 content.notify.interval : 750000 content.notify.ontimer : true content.switch.threshold : 750000 content.maxtextrun : 8191 content.max.tokenizing.time : 3000000 signed.applets.codebase_principal_support : true Edit: Note that the network settings that give the best speed improvements often depend on your configuration, so you might need to experiment with it to get the best results. |
||
Edited by unstable on 18.09.2006 22:14:35 | |||
18.09.2006 22:08:59 |
|
||
Grivier |
that's a good idea, s-k maybe that will help me solve all of them if i find anything new,i'll post it... i think i have something for opera too but have to search on pc Grivier |
||
19.09.2006 08:56:41 |
|
||
unknown user |
It should probably be noted that there is a reason why this not set to default, or runtime detected. The reason? Not all servers work with these pipelining settings. Some will flag the rappid connections as an abuse/attack, and the firewall would block you out. read more here http://gentoo-wiki.com/TIP_Firefox_Settings#Pipelining |
||
19.09.2006 12:00:16 |
|
||
Grivier |
i know, if network.http.pipelining.maxrequests is put on a large number, sites might be thinking you're hammering and ban you out...but it also works while it works Grivier |
||
Edited by Grivier on 19.09.2006 13:25:53 | |||
19.09.2006 13:25:29 |
|