Web Hosting Talk : Other Forums : Web Hosting Lounge : Firefox pipelining = server rape?

[Techno]

http://forevergeek.com/open_source/m...fox_faster.php'

http://www.pcmag.com/article2/0,1759,1748707,00.asp

snipped...

To boost Firefox, simply do the following after launching your browser.

1. Type "about:config" into the address bar (no spaces) 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 at a time to a Web page. When you enable pipelining, the browser 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 tells the browser to 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 acting on received information.

Okay. That's all it takes. But now let's dig into the controversy that is foaming up discussion boards across the land. The term the hard core use for opening 30 server calls at one time is not pretty, but says it all: server raping. Taking up 30 simultaneous sessions is a major don't, since most servers bomb out at around 100. If four people using this tweak hit a page at the exact same time, they would crash everything, warned many a geek.

But not so, according to the other camp, who explain that pipelining is not about opening multiple sessions but simply changing how a single session pulls down information. The irony is that most developers gave up on pipelining after broadband became more widespread, and browsers today ship with this default set to "Off" or "False" to protect servers from throwing up bugs during a rapid pipeline burst.

[Aea]

Sexy Fast, now if only firefox would be the default browser as I set it *grumbles*.

[Lev]

Yes, firefox pipelining does equal server rape . Well, it uses a lot of bandwidth and some server resources anyway.

Originally posted by Aea
Sexy Fast, now if only firefox would be the default browser as I set it *grumbles*.

Ditto. I wish my firefox would do the same.

[Webdude]

I downloaded then removed firefox a few weeks ago as it really wasnt any faster in loading pages than my IE. I just downloaded it and reinstalled it, did what was posted here....and dang it loads pages fast..... even WHT which is typically pretty slow for me even on my 3 meg connection.

I think you finally gave me a good enough reason to switch!

[Knogle]

Are there similar options for IE?

[Blankwire]

Originally posted by Knogle
Are there similar options for IE?

I believeyou need to do a registry hack for something like that.

[Paul]

Remeber the hard coded pipe limit is 8, you can set it higher but wont help

[Knogle]

ProjectB, is there any guide you can refer me to, which will enable me to accomplish that?

[Techark]

NO it is not server rape it is pipelining it is not opening 30 different connections at once it is simply keeping the connection open and allowing faster loads of images etc.

I suggest you read up on pipelining or better yet set your browser up and load your own web page and watch the connections on your own server before proclaiming it is raping the server and using massive amounts of bandwidth. Besides if it opened a hundred connections at once what diffference would it make in bandwidth ? It is only going to download the content of the web site so how is doing 30 downloads at a time different from doing 30 downloads of the same content one after the other going to change the bandwidth it uses? Same 30 web page elements are downloaded.

[Blankwire]

Originally posted by Knogle
ProjectB, is there any guide you can refer me to, which will enable me to accomplish that?

I can't seem to find it anywhere now, but I know I saw it. Try Google.

[mp3LM]

Originally posted by Techark
NO it is not server rape it is pipelining it is not opening 30 different connections at once it is simply keeping the connection open and allowing faster loads of images etc.

I suggest you read up on pipelining or better yet set your browser up and load your own web page and watch the connections on your own server before proclaiming it is raping the server and using massive amounts of bandwidth. Besides if it opened a hundred connections at once what diffference would it make in bandwidth ? It is only going to download the content of the web site so how is doing 30 downloads at a time different from doing 30 downloads of the same content one after the other going to change the bandwidth it uses? Same 30 web page elements are downloaded.

Throughput would change, would it not?

[slice16]

coooool now thats fast