Re: dpkg
Ben Collins wrote:
> As it reads, it is allocating memory for, and creating a very large in
> memory structure. I think it also verifies the files associated with the
> package, and does some other sanity checks.
It's not looking at any other files according to strace.
> IMO, about the only way to
> get real speedup is for all of this data to be in a hashed database,
> on disk, so all dpkg has to do is open the database and verify files.
> The hash will already be avaiable. However, there are probably some
> caveats to this.
Well another useful optimization would be to not read the available file
at all if nothing it is going to do involves the available file.
I've just zeroed mine out, sigh.
--
see shy jo
Reply to:
- Follow-Ups:
- Re: dpkg
- From: Ben Collins <bcollins@debian.org>
- References:
- dpkg
- From: Joey Hess <joeyh@debian.org>
- Re: dpkg
- From: Joey Hess <joeyh@debian.org>
- Re: dpkg
- From: Ben Collins <bcollins@debian.org>