Add per-page caching of filtered and rendered tours

Created on 2 July 2013, over 11 years ago
Updated 5 September 2024, 3 months ago

Updated: Comment #0

Problem/Motivation

Tour module loads all tour config entities on every page and then filters them down to those required for that page. As these are relatively static objects they should be cached per page so subsequent views of the page don't require the full round trip again. This code existed in the original patch but was identified as 'premature optimisation' and subsequently removed.

Proposed resolution

Add back the per-page caching of tours and profile the performance improvement.

Remaining tasks

Write the patch
Add tests
Profile it
Review

User interface changes

None

API changes

None

Related Issues

#1744302: [meta] Resolve known performance regressions in Drupal 8 β†’

πŸ“Œ Task
Status

Closed: outdated

Version

2.0

Component
TourΒ  β†’

Last updated 1 day ago

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

Live updates comments and jobs are added and updated live.
  • needs profiling

    It may affect performance, and thus requires in-depth technical reviews and profiling.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024