branch scanner is running too slow for 1 minute cron interval.

Bug #105949 reported by Diogo Matsubara
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Unassigned

Bug Description

Branch scanner routinely overruns its one minute time slot, causing lockfile contention and errorspam.

According to David, one possible cause is:

<ddaa> the new branch email stuff generates a diff for ever new history revision found in a branch
<ddaa> regardless of whether it's going to be used

Tags: lp-code
David Allouche (ddaa)
description: updated
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Can certainly confirm this,

Part of the problem may be that after the supermirror-pull.py mirror script has hung (bug #121331) and been restarted, the last mirrored time of all the mirror branches will tend very much to cluster, which means that suddenly the branch-scanner gets a lot more work to do.

Changed in launchpad-bazaar:
status: New → Confirmed
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

That said, after elmo did whatever he had to do to get apache on the supermirror behaving, this problem has more or less gone away again. Still a waste of resources though.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

The scanner performance is going to be more and more of a problem as traffic increases. It's not yet High priority yet though, IMHO.

Changed in launchpad-bazaar:
importance: Undecided → Medium
Revision history for this message
Aaron Bentley (abentley) wrote :

This seems to have been largely fixed by splitting it out into jobs. There are performance issues, but only when there are hundreds of branches to scan, which is not unreasonable, and seems to deserve its own bug.

Changed in launchpad-code:
status: Triaged → Fix Released
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.