[Apt-cacher-ng-users] Simultaneous retrieval not being cached?

[Eduard Bloch]

#include <hallo.h>
* Anshuman Aggarwal [Tue, Nov 22 2011, 03:49:14PM]:
> Hi,
>  Thanks for apt-cacher-ng. Works well when the file has been retrieved
> completely.
> 
> However, if two or more clients are trying to request the same file at the
> same time (as can happen when people are upgrading in an office)…it appears

First: please report at least the version used there.

> that the partial file already downloaded is not being cached (possibly
> because the in-memory retrieved file has not been added to the database
> used for retrieval/filesystem)…I'm pretty sure this is happening as the
> download bandwidth gets halved then goes to a third when simultaneously
> upgrading packages…any chance someone who has looked at the code can quirky
> confirm this?
> Based on that it is either a bug or a feature request..

apt-cacher-ng was designed to explicitly support this usage pattern,
considering all rules of concurency.

In fact, I can not reproduce this issue... (DON'T DO THIS AT HOME)

for x in `seq 10` ; do ( curl -s http://localhost:3142/ftp.fr.debian.org/debian/pool/main/n/nexuiz-data/nexuiz-data_2.5.2-6_all.deb > /dev/null & ) ; done

and "iftop -B -i lo" shows me phantastic throughput, almost factor 10
compared to the progress of:

watch -n1 du /var/cache/apt-cacher-ng/debrep/pool/main/n/nexuiz-data/nexuiz-data_2.5.2-6_all.deb

Please check your log and make sure the files are resolved to the
same cache locations.

Regards,
Eduard.
-- 
<pasc> man
<pasc> the AMD64 camp is not helped by the list of people supporting it
<pasc> when nerode is on your side, you know you're doing something wrong