Re: Bug#622322: popularity-contest: popcon tries to access dpkg internal files and fails with multiarch: same packageso
On Sat, May 07, 2011 at 06:45:03PM +0200, Raphael Hertzog wrote:
> On Sat, 07 May 2011, Bill Allombert wrote:
> > Thanks, please find a popularity-contest script that uses dpkg -L by batch.
> > The size of the batch is $dpkg_batch_size at the start of the script.
> > Below are timings on my laptop (with a fast solid-state disk):
> > Direct access : 2.214 s
> > batch of 1 pkg : 31.446 s
> > batch of 2 pkgs: 5.218 s
> > batch of 3 pkgs: 2.652 s
> > batch of 4 pkgs: 2.405 s
> > batch of 5 pkgs: 2.395 s
> > batch of 8 pkgs: 2.380 s
> > batch of 10 pkgs: 2.370 s
> > batch of >=10 pkgs: about 2.370 s
> > Please test with multiarch.
> Thanks, seems to work fine, I have no error/warning at least.
> batch of 1 pkg: 3m10.789s
> batch of 2 pkgs: 0m21.769s
> batch of 3 pkgs: 0m6.362s
> batch of 4 pkgs: 0m4.763s
> batch of 5 pkgs: 0m4.714s
> batch of 10 pkgs: 0m4.670s
> Direct access: 0m4.637s
OK, so you get comparable results. It is very odd that there so much a difference between
batch of 1 package and batch of 2 packages. Maybe this is a dpkg issue ?
Also, how does dpkg -L handles the dpkg lock ?
Imagine a large red swirl here.