scan_branches uses too much memory, bogs down machine

Bug #690512 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

Following on from bug 690021, about scan_branches bogging down the machine:

Apparently scan_branches.py uses a lot of memory scanning some linux import branches. We should work out why and fix it. Log in https://pastebin.canonical.com/40916/

Tags: lp-code
Martin Pool (mbp)
Changed in launchpad-code:
importance: Undecided → Medium
status: New → Confirmed
Curtis Hovey (sinzui)
Changed in launchpad:
status: Confirmed → Triaged
Changed in launchpad:
importance: Medium → High
Revision history for this message
John A Meinel (jameinel) wrote :

Isn't this because scan_branches grabs the whole history of the branches, to figure out what is 'new' to be imported, rather than incrementally walking them to see what is missing? I don't fully understand what bzr needs to do here.

Changed in bzr:
importance: Undecided → Low
status: New → Incomplete
Jelmer Vernooij (jelmer)
no longer affects: bzr
Revision history for this message
Robert Collins (lifeless) wrote :

@john I think the theory is that holding just the revids for all of e.g. linux shouldn't be a memory burden in and off itself, that something else is causing the issue (e.g. fragmentation, bzr caches ...)

summary: - scan_branches uses too much memory
+ scan_branches uses too much memory, bogs down machine
Revision history for this message
Martin Pool (mbp) wrote :

This doesn't need a bzr specific task unless/until we determine the problem is actually internal to bzr. Diagnosis needs to start on the lp side.

no longer affects: bzr
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.