Status: Closed (View Workflow)
- blueocean.js (642KB), 370 ms to load: is loaded on each page (dashboard, run details, pipeline)
- Cache expiry for assets that never change is very low (e.g. fonts)
- And so are most other JS files
- If these are cached (not fetched for each page can easily save few secs)
For details see
JENKINS-38079 Investigate performance degradation report
- is related to
JENKINS-38882 Avoid browser cache busting after Jenkins restart
JENKINS-38881 Cache CSS in localStorage
I know all assets are fetched via the Jenkins "adjuncts" which includes a hash in the URL. Just curious, what controls the generation of this hash?
cliffmeyers it is generated on startup (the hash) - so each restart will make things reload
tfennelly I'm happy to take on an optimization to the BO plugins' CSS. It's not as critical of a thing for performance reasons, but other reasons I'd like to change the behavior and optimize at the same time.
We added cache-control headers for all adjunct and static URLs (covering most JS, CSS , fonts etc). Time will tell us if that's helping.
Right so the remaining issue is more about the multiple loading of blueocean.js - (is that still a valid problem?)
michaelneale no, that should not be happening unless you hit a hard reload. It's expected that you guys out in the sticks in Aus are supposed to get the greatest benefit from this, so let us know.
it seems a lot better on the whole, but that is subjective.
In the ticket description, vivek mentions multiple loading of blueocean.js though ... that is what I meant
I can only assume he was talking about the multiple If-Modified-After request. These are not happening anymore.
vivek font caching too. Lots of immutable resources have very low cache expiry (I think 24 hours)