A tip for all you guys with slow PCs
Discussion
Please don't bury this one in the Computers section, because it's aimed at those who aren't techno geeks but are instead soldiering on with a slow PC. If you're running Firefox and have access to a broadband connection (not wireless), here's a tip that will cut page loading and some download times virtually in half. 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.
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.
3. 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.
4. Right-click anywhere and select New-> Boolean.
Name it "browser.turbo.enabled" and set its value to "True"
Ba-da bing. You should be good to go. Check it out.
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.
3. 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.
4. Right-click anywhere and select New-> Boolean.
Name it "browser.turbo.enabled" and set its value to "True"
Ba-da bing. You should be good to go. Check it out.
It works, Oh yes, it works.
Impressed!! Know any more good ones. Plotloss said:
This Firefox tuning malarky has a cost, at the webserver end, so expect to see a few pissed off webmasters as their servers get assaulted with more requests than usual...
I've heard this before too - I believe in simple terms instead of requesting each item one by one (i.e. pics etc) it asks for everything all at once and has multiple instances downloading (think in this way - instead of filling a pool up with one hose - you use five hoses instead - thus allow five times the fill rate).
This has an effect of putting excess load on webservers and bandwidth and so pissing off the webmasters...
But then again
I may stand corrected on the above if I got in wrong
I'm not sure what the above is meant to do.
IIRC the original http1.0 spec was pretty plain, and to get multiple images you would create multiple simultaneous requests. this results in say 5 images all downloading slowly but at once
http1.1 which has been around for a very long time was able to queue requests to a single web daemon running on the webserver itself.
this enabled you to downlad all 5 images one after another without adding any extra processes to the web server itself. the end result was that the page built itself up one graphic at a time giving the impression of a faster connection, but because you are downloading the same 5 images the download rate should be the same.
eg 5*1 vs 1*5.
however, with broadband, by setting it to make multiple requests (like in the http1.0 days) you open 5 connections at once to download all 5 images. although many webservers now can deliver a huge amount of data very quickly, the daemons that deliver the data sometimes arent very fast. so, if you have a large pipeline and commandeer 5 daemons to download your pages you could get a faster download time than using the a single daemon to download 5 objects.
and then heres where it gets very odd. built within http1.1 (if i remember correctly) it will only queue requests (eg 1 graphic at a time) if the server is reaching its max number of daemons. at that point the server switches into a different mode so that it can deal with more clients.
so the person who said they got a broken graphic - you got that because the webserver you were dealing with was at a max limit and refused the connection because it saw you trying to do something clever.
>> Edited by tinman0 on Sunday 23 October 17:39
IIRC the original http1.0 spec was pretty plain, and to get multiple images you would create multiple simultaneous requests. this results in say 5 images all downloading slowly but at once
http1.1 which has been around for a very long time was able to queue requests to a single web daemon running on the webserver itself.
this enabled you to downlad all 5 images one after another without adding any extra processes to the web server itself. the end result was that the page built itself up one graphic at a time giving the impression of a faster connection, but because you are downloading the same 5 images the download rate should be the same.
eg 5*1 vs 1*5.
however, with broadband, by setting it to make multiple requests (like in the http1.0 days) you open 5 connections at once to download all 5 images. although many webservers now can deliver a huge amount of data very quickly, the daemons that deliver the data sometimes arent very fast. so, if you have a large pipeline and commandeer 5 daemons to download your pages you could get a faster download time than using the a single daemon to download 5 objects.
and then heres where it gets very odd. built within http1.1 (if i remember correctly) it will only queue requests (eg 1 graphic at a time) if the server is reaching its max number of daemons. at that point the server switches into a different mode so that it can deal with more clients.
so the person who said they got a broken graphic - you got that because the webserver you were dealing with was at a max limit and refused the connection because it saw you trying to do something clever.
>> Edited by tinman0 on Sunday 23 October 17:39
Gassing Station | The Pie & Piston Archive | Top of Page | What's New | My Stuff