GoFuckYourself.com - Adult Webmaster Forum - View Single Post

raymor · 03-05-2008, 12:12 PM

I, and others responding, misread the "40" for network.http.pipelining.maxrequests
as maxconnections. For the maximum number of connections somewhere
between two and four is good.

The maximum pipelining requests tells how many requests should be sent over
a single connection before the server responds to the first one. Pipelining is
helpful mainly to users with connections with high throughput but very poor
latency, such as satellite connections. That is, if you have a high Mbps
connection but ping times are poor. In additon, it is only helpful if the
page contains many small images smaller than 10KB or so. Over 10 KB,
download throuput is the limiting factor. Very high numbers for maxrequests
make the page appear slower in a fashion similar to a high number of
maxconnections, so Firefox will totally IGNORE you if you try to set this
higher than TEN. That last part bears repeating - setting maxrequests to
forty is such a bad idea that Firefox will laugh you off and ignore the setting
entirely. So in summary, if you're on a satellite connection or you're in the
Anarctic far from any web servers but have a high speed connection, set
maxrequests to six. For the other 99.99% of users, three is a good choice.
Some web servers can't do pipelining, so pages won't load at all. That's
why IE and Firefox have it turned off by default - not because the Firefox
developers aren't as smart as CunningStunt. That's true generally - the Firefox
developers know all about all of this stuff. They chose the default settings
for good reasons after extended discussion amongst serious geeks.
Unless you REALLY understand these things and think you're smarter than
the people who wrote Firefox in the first place, anything you chnage is likely
to hurt performnce and reliability, not help.

03-05-2008, 12:12 PM
raymor Confirmed User Join Date: Oct 2002 Posts: 3,745	I, and others responding, misread the "40" for network.http.pipelining.maxrequests as maxconnections. For the maximum number of connections somewhere between two and four is good. The maximum pipelining requests tells how many requests should be sent over a single connection before the server responds to the first one. Pipelining is helpful mainly to users with connections with high throughput but very poor latency, such as satellite connections. That is, if you have a high Mbps connection but ping times are poor. In additon, it is only helpful if the page contains many small images smaller than 10KB or so. Over 10 KB, download throuput is the limiting factor. Very high numbers for maxrequests make the page appear slower in a fashion similar to a high number of maxconnections, so Firefox will totally IGNORE you if you try to set this higher than TEN. That last part bears repeating - setting maxrequests to forty is such a bad idea that Firefox will laugh you off and ignore the setting entirely. So in summary, if you're on a satellite connection or you're in the Anarctic far from any web servers but have a high speed connection, set maxrequests to six. For the other 99.99% of users, three is a good choice. Some web servers can't do pipelining, so pages won't load at all. That's why IE and Firefox have it turned off by default - not because the Firefox developers aren't as smart as CunningStunt. That's true generally - the Firefox developers know all about all of this stuff. They chose the default settings for good reasons after extended discussion amongst serious geeks. Unless you REALLY understand these things and think you're smarter than the people who wrote Firefox in the first place, anything you chnage is likely to hurt performnce and reliability, not help. __________________ For historical display only. This information is not current: support@bettercgi.com ICQ 7208627 Strongbox - The next generation in site security Throttlebox - The next generation in bandwidth control Clonebox - Backup and disaster recovery on steroids