bugsummary_rollup_journal is slow

Bug #810104 reported by Stuart Bishop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Stuart Bishop

Bug Description

The bugsummary_inc and _dec stored procedures are slow, making the rollup process slow.

Rework the UPDATEs to not use IS DISTINCT FROM and see if we can make use of the indexes instead of full table scans.

Tags: qa-ok timeout

Related branches

Stuart Bishop (stub)
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Stuart Bishop (stub)
Revision history for this message
Stuart Bishop (stub) wrote :

We think this may be exacerbating timeouts due to row locks.

Changed in launchpad:
importance: High → Critical
tags: added: timeout
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Revision history for this message
Robert Collins (lifeless) wrote :

cold, on qastaging with 600 summary changes:
lpmain_staging=# select count(*) from bugsummaryjournal;
 count
-------
   603
(1 row)

lpmain_staging=# explain analyze select bugsummary_rollup_journal();
                                        QUERY PLAN
------------------------------------------------------------------------------------------
 Result (cost=0.00..0.26 rows=1 width=0) (actual time=8543.085..8543.086 rows=1 loops=1)
 Total runtime: 8543.112 ms
(2 rows)

lpmain_staging=# select count(*) from bugsummaryjournal;
 count
-------
     0

so its at least working, though whether it fixes the performance issue I'm not sure.

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.