Bug#149760: dpkg: should use something faster than text files
- To: email@example.com
- Subject: Bug#149760: dpkg: should use something faster than text files
- From: Francois-Rene Rideau <firstname.lastname@example.org>
- Date: Wed, 12 Jun 2002 14:12:47 +0200
- Message-id: <20020612121247.GA27386@ZhengHe.augustin.thierry>
- Reply-to: Francois-Rene Rideau <email@example.com>, firstname.lastname@example.org
- In-reply-to: <20020612114920.GC12809@ZhengHe.augustin.thierry>
- References: <20020612114920.GC12809@ZhengHe.augustin.thierry>
dpkg is much slower than rpm, especially on machines with less
than 256MB of RAM, due to its using thousands of text files
instead of preparsed, preindexed, files that could be directly mmap()ed,
or otherwise directly used with an efficient database API.
I understand the need for text configuration files at the source level,
and for them as a canonical interchange format.
But shouldn't the .deb package packing, unpacking and indexing software
preprocess those files into something much more efficient?
Simple things like dpkg -S, or just the initial parsing of files
before any dpkg -i, take quite a lot of time, while heavily loading
the machine, in a way coupled with the need for someone to supervise
installation, due to questions being asked, so it can't be done
while the operator is away or asleep
(maybe I should try different settings on question priority).
Just my .2 mg of gold worth.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
[ TUNES project for a Free Reflective Computing System | http://tunes.org ]
The idea that a human being should always be accessible to a computer.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org