To participate you must create an account on apostrophenow.org. If you have already done so, click Login.

Ticket #81 (closed defect: fixed)

Opened 2 years ago

Last modified 21 months ago

Evaluate the performance impact of getTreeInfo

Reported by: boutell Owned by: boutell
Priority: major Milestone: 1.4
Component: Documentation Version: 1.0
Keywords: performance Cc: dordille, agilbert
Symfony version: 1.4

Description

We have get*Info methods for smaller subsets of the page tree, but calling getTreeInfo just once and then outputting breadcrumb, tabs and side nav turns out to run rather well. However we need to test this with a much larger database to see how the performance is with 1000 or more pages. We're not making objects and the query is raw PDO, so it may still turn out to be good.

Long term we should think about using the symfony function call cache to further accelerate these methods, clearing that cache when page objects are saved or deleted.

Change History

Changed 2 years ago by boutell

Also, consider whether getAccordionInfo could be the basis call instead of getTreeInfo, that would be a simple fix (double check whether they return an identical data structure)

Changed 2 years ago by boutell

  • status changed from new to accepted

Changed 21 months ago by boutell

  • status changed from accepted to closed
  • resolution set to fixed

We hit this, we no longer use getTreeInfo by default.

Note: See TracTickets for help on using tickets.