Add extra page request to the across pages asset performance test

Created on 5 May 2024, about 2 months ago
Updated 26 June 2024, 2 days ago

Problem/Motivation

Split from 📌 Use placeholdering for more elements to optimize asset serving Needs work , if we add more pages from Umami, we get a better 'worst case scenario' for the current aggregation / library organisation to improve from.

Steps to reproduce

Proposed resolution

Visit an extra page during these two test methods. Because this loads a different, third, combination of libraries to the first two pages, it results in a different set of asset aggregates and therefore more files and overall bytes being downloaded.

Issues like 📌 Use placeholdering for more elements to optimize asset serving Needs work which attempt to reduce duplication between asset aggregates in this kind of scenario will then be able to show an improvement (or not) based on the existing test scenario.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Fixed

Version

11.0 🔥

Component
Asset library 

Last updated about 16 hours ago

No maintainer
Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.69.0 2024