On Mon, 2007-08-06 at 09:24 +0200, Florian Festi wrote: > While doing my sqlite indexes tests I realized that VACUUMing the sqlite db > heavily influences the performance. The non VACUUMed sqlite db needs 28 > seconds to rebuild the indexes while an vacuumed/fresh db can build them in > 6 seconds. > > So I was wondering if this has any impact on the current yum. Although I > didn't realize that myself yet a colleague of mine often complains that > updating the sqlite db takes a long time. Does anyone else see this > behavior? If this is an real issue we should consider calling VACUUM; from > time to time.
Maybe we should just do the vacuum when creating the sqlite db in createrepo. Since in most cases, that's what people are going to be grabbing at this point. Not sure what sort of heuristics would make sense for an automatic vacuum when we're doing the incremental updates, though. Jeremy _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
