[Apt-cacher-ng-users] slow "apt-get update" via apt-cacher-ng

[Kirill Timofeev]

Hi Eduard,

I'm sorry to bother you. Please let me know if I can provide more 
information to help with issue analysis.

Thanks,
Kirill.

On 07/29/2014 02:15 PM, Kirill Timofeev wrote:
> Hi Eduard,
>
> 500 errors were because of misconfigured internal repository 
> pkg.prod.hulu.com (https://github.com/hulu/urepo). I fixed issue and 
> run command again:
>
> root at els-trusty-test-02:~# time apt-get update -o 
> Debug::Acquire::Http=true >apt-cacher-ng-slow-update.log 2>&1
>
> real    0m40.026s
> user    0m4.041s
> sys     0m0.603s
> root at els-trusty-test-02:~#
>
> New log is attached, update time unfortunately is still quite long.
>
> Thanks,
> Kirill.
>
> On 07/29/2014 01:54 PM, Eduard Bloch wrote:
>> Hallo,
>> * Kirill Timofeev [Mon, Jul 28 2014, 11:43:13PM]:
>>> Hi Eduard,
>>>
>>> thank you very much for quick response. Please find log attached. 
>>> Here is
>>> command I used to obtain this log:
>>>
>>> root at els-trusty-test-02:~# time apt-get update -o 
>>> Debug::Acquire::Http=true
>>>> apt-cacher-ng-slow-update.log 2>&1
>>> real    0m39.796s
>>> user    0m4.212s
>>> sys     0m0.626s
>>> Ign http://us.archive.ubuntu.com trusty InRelease
>>> HTTP/1.1 500 Internal Server Error
>>> Content-Length: 0
>>> Date: Tue Jul 29 06:40:20 2014
>>> Server: Debian Apt-Cacher NG/0.7.26
>>> X-Original-Source: 
>>> http://pkg.prod.hulu.com/deb/dists/trusty/Release.gpg
>>> Connection: Keep-Alive
>> There is a lot of such error messages in your log. However,
>> apt-cacher-ng does not generate them! There is only one similar string
>> in the source which uses different letter case ("500 Internal server 
>> error").
>>
>> This leads me to the assumption that you must have something inbetween
>> (another proxy that rewrites the responses incorrectly?) which goes 
>> nuts.
>> Maybe a transparent proxy which you don't know anything about?
>>
>> If that assumption is correct, you might play around with PipelineDepth
>> option until you find a value which this proxy is willing/capable to
>> handle.
>>
>> Regards,
>> Eduard.
>