update-pkgcache.py is extremely slow
Bug #712284 reported by
William Grant
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
update-pkgcache.py currently takes more than 15 hours to run on production. A lot of this is probably spent creating package cache objects for PPAs and copy archives; they're unused except by updateArchiveCache, so there's probably a better way.
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| tags: | added: fdt |
Revision history for this message
| William Grant (wgrant) wrote | #2 |
To post a comment you must log in.
We definitely don't need caches for copy objects, they can be taken out right away (and clear up the DB).
PPAs are a different matter, but we could probably reduce the time it takes by being more intelligent about which PPAs we're scanning.