Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Removing pipelining works great' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Removing pipelining works great
Authored by: uid73397 on Jan 26, '03 01:15:52AM

I made my pipelining options false and the increase in speed was huge. I have the 4 line, multiple connections addition referred to in this post but with the following numbers:

user_pref("network.http.max-connections", 128);
user_pref("network.http.max-connections-per-server", 48);
user_pref("network.http.max-persistent-connections-per-proxy", 24);
user_pref("network.http.max-persistent-connections-per-server", 12);



[ Reply to This | # ]
Removing pipelining works great
Authored by: mosch on Jan 28, '03 11:19:48AM

Please don't even consider using the settings that uid73397 has suggested. 48 connections per server might give you decent performance, but it does so by slamming the load on the server, and is actually fairly likely to cause you some delay, due to the server being unable to provide that many connections immediately.

The default apache configuration allows a total 150 concurrent connections, with 8 spares at any given time, because individual users are expected to use between a few connections. Telling the browser to initiate 48 connections to the server simultaneously means that you could potentially be using one third of a heavy-duty server's connections for a moment. The worst part is that if the admin has attempted to improve overall quality of service by limiting per IP bandwidth to something reasonable, all those connections will stay open for a significant amount of time.

Well, I'm off to see what I need to do to limit connections per IP, since uid73397 has accidentally pointed out a denial-of-service attack that I'd never previously considered.

Please don't follow this anti-social "hint".



[ Reply to This | # ]