| 2012-05-11 00:45:10 |
Scott Moser |
description |
Per UDS session on Apt improvements, it has been proposed to remove apt http pipelining
The reasons:
1. HTTP Pipelining has issue with certain proxy implementation
2. Some new object stores, like S3, or Google's APT repositories have problems with HTTP Pipelining
Running a test shows that disabling apt-pipelining has no perceptable diffferenvce, and disabling apt pipeling actually performed slightly better with an average of 31.899s versuses 32.456s. I tested an "apt-get -y update" with and without apt HTTP pipelining turned on.
Pipelining on (apt-get -y upgrade):
33.92
31.37
31.64
31.63
33.29
33.08
32.92
32.88
31.73
31.98
32.01
32.96
31.51
32.68
33.25
Pipelining off (apt-get -o Acquire::http::Pipeline-Depth="0" -y upgrade):
31.66
31.59
31.24
31.30
31.29
32.85
32.75
31.50
31.18
32.26
31.43
33.28
31.67
32.45
32.04 |
Per UDS session on Apt improvements, it has been proposed to remove apt http pipelining
The reasons:
1. HTTP Pipelining has issue with certain proxy implementation
2. Some new object stores, like S3, or Google's APT repositories have problems with HTTP Pipelining
Running a test shows that disabling apt-pipelining has no perceptable diffferenvce, and disabling apt pipeling actually performed slightly better with an average of 31.899s versuses 32.456s. I tested an "apt-get -y update" with and without apt HTTP pipelining turned on.
For more information on apt-pipelining, here are 2 threads to read:
http://old.nabble.com/APT-do-not-work-with-Squid-as-a-proxy-because-of-pipelining-default-td28579596.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565555
Pipelining on (apt-get -y upgrade):
33.92
31.37
31.64
31.63
33.29
33.08
32.92
32.88
31.73
31.98
32.01
32.96
31.51
32.68
33.25
Pipelining off (apt-get -o Acquire::http::Pipeline-Depth="0" -y upgrade):
31.66
31.59
31.24
31.30
31.29
32.85
32.75
31.50
31.18
32.26
31.43
33.28
31.67
32.45
32.04 |
|
