Launchpad itself

Cache POTemplate.displayname

Bug #60320 reported by Christian Reis
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Unassigned

Bug Description

Generating POTemplate.displayname (and .title) is pretty expensive -- they require hitting 4 or 5 other tables for each call. This is significant overhead for certain templates, such as object-pots and person-translations. Generating a cached column would speed up things significantly here.

Revision history for this message
Christian Reis (kiko) wrote :

If the fix for bug 2497 lands and +translations is still [soft] timing out, we should do this.

Changed in rosetta:
assignee: nobody → kiko
Revision history for this message
Carlos Perelló Marín (carlos) wrote :

Seems like it's not needed.

Changed in rosetta:
status: Unconfirmed → Rejected
Revision history for this message
Carlos Perelló Marín (carlos) wrote :

Reopened per kiko suggestion.

Changed in rosetta:
status: Rejected → In Progress
Christian Reis (kiko)
Changed in rosetta:
assignee: kiko → nobody
importance: Undecided → Medium
status: In Progress → New
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

The "phase 2" schema refactoring reduced the numbers of extra tables to 2—3, so up to 150 records for a standard 50-entry +translations page. In practice it'll be hard to get anywhere near that number, but we do still see some timeouts.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

It's only two extra tables at the moment, and for longer listings, ones that are relatively likely to be cached already. Also, our ORM caches more aggressively now so I don't think this makes much sense anymore.

Changed in rosetta:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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