update-bugtask-targetnamecaches is horrifyingly inefficient

Bug #718004 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
William Grant

Bug Description

update-bugtask-targetnamecaches is currently taking 20 hours to run on production (although it can run in 8). It grabs every bugtask and updates it separately. There are lots of bugtasks.

As a quick optimisation we can select all distinct targets and do a group update. Eventually we probably want to drop the targetnamecache field, or fire off a job to update it when a target is renamed.

Tags: qa-ok

Related branches

William Grant (wgrant)
Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.03
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → 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.