Updated: Comment #0
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.
Add back the per-page caching of tours and profile the performance improvement.
Write the patch
Add tests
Profile it
Review
None
None
#1744302: [meta] Resolve known performance regressions in Drupal 8 →
Active
2.0
It may affect performance, and thus requires in-depth technical reviews and profiling.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This extension is being deprecated, see 🌱 [Meta] Tasks to deprecate Tour module Active . It will be removed from core and moved to a contrib project, 📌 [11.x] [Meta] Tasks to remove Tour Postponed .
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.