On Jul 18, 2007, at 1:38 PM, Robert Scheck wrote:
Evening folks,
On Wed, 18 Jul 2007, Jeff Johnson wrote:
Using flat files avoids all the complexity of rpmdb iterator methods,
maximizes access of installed information because only files need
to be
opened, and permits 3rd party software installers to simply write
their
metadata file goop to the file system, no fuss no muss.
well...so far so good. What's up to the performance? Is a flat file
rpmdb
faster rather Berkeley DB? IIRC a sqlite rpmdb is about 2.3 times
slower
(averaged) rather a Berkeley rpmdb. A switch sounds interesting,
but it's
maybe a question of pain.
My proposal was not for a single flat file, but rather for using
directories
to contain files with names that happen to "group" together. The name
itself reduces the amount of information that needs to be processed.
A single flat file with an offset can be substituted that is at least
as well
performing, but the implementation is more subtle because one needs
to keep track of the offset value to debug the mess. Not true for files
in a directory, ls -al suffices.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
