Skip to content

perf: cache the nuxt-og-image font download in build_website - #213

Open
dimitrieh wants to merge 3 commits into
mainfrom
build-website-og-image-font-cache
Open

perf: cache the nuxt-og-image font download in build_website#213
dimitrieh wants to merge 3 commits into
mainfrom
build-website-og-image-font-cache

Conversation

@dimitrieh

Copy link
Copy Markdown
Contributor

Ports the og-image cache step from FlowFuse/website's test.yml into the shared build. FlowFuse/website#5515 replaces that job with a call to this workflow, and a job that uses a reusable workflow takes no steps of its own, so the step has to live here or not at all.

Narrowed while porting. Measured on website main:

with cache without
Build the forge 1359s 1394s
entry size / restore 2.5 MB / 1s n/a

The github.run_id key wrote a fresh entry every run, 53 of them live. Only the font download is worth keeping, so this caches that one directory keyed on the lockfile that pins the module: an unchanged lockfile hits exactly and saves nothing back.

perf: means the release job moves build_website/v1, so website #5515 picks this up without a ref change.

Happy to drop it entirely if you would rather the shared build carry no og-image cache.

FlowFuse/website's own test.yml cached two directories under a github.run_id
key, so every run wrote a fresh entry. Measured on website main, the entry is
2.5MB, restores in 1s, and 53 of them were live. Build the forge took 1359s
with it against 1394s without, so the render directory was buying nothing.

This keeps only the font download, keyed on the lockfile that pins the module,
so an unchanged lockfile hits exactly and saves nothing back.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant