Add draft field note: sccache compile cluster on Chromium (build-cluster-chromium) - #465
Draft
jetm wants to merge 3 commits into
Draft
Add draft field note: sccache compile cluster on Chromium (build-cluster-chromium)#465jetm wants to merge 3 commits into
jetm wants to merge 3 commits into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new draft Field Note documenting measurement-driven results from using a two-machine sccache-dist compile cluster to accelerate Yocto builds, emphasizing the difference between a single compile-bound package (Chromium) vs. an end-to-end image build.
Changes:
- Introduces a new draft Field Note MDX post with
[ENGINEER:]placeholders for pending measurements and demo embeds. - Documents observed outcomes and constraints (compile-bound vs configure/latency-bound behavior) and frames follow-on work.
- Links the “what broke / what we’re upstreaming” section to public
mozilla/sccachetracking (RFC #2775 and PRs #2776/#2777).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jetm
force-pushed
the
field-notes/build-cluster-chromium
branch
from
July 21, 2026 18:32
41888f0 to
a4a5828
Compare
…ter-chromium) Structured draft (draft: true) with [ENGINEER:] placeholders for the recorded Chromium demo numbers and the feed package count; it stays on the branch until the demo is recorded and the placeholders are filled. Frames the compiler-cache cluster honestly (big on the compile-bound package, ~11% on a full image) and links the mozilla/sccache upstreaming. Tracks ENG-2174. Signed-off-by: Javier Tia <javier@peridio.com>
jetm
force-pushed
the
field-notes/build-cluster-chromium
branch
from
July 21, 2026 18:45
a4a5828 to
f577c5a
Compare
TestStatus renders whatever `cli` receives under a hard-coded "Avocado CLI" label. This note passed a build-tooling version into it, so the rendered strip would have claimed an Avocado CLI version the note never tested against - and the value is a placeholder, so the wrong label would have survived the fill-in pass unnoticed. The build-tooling version is already carried by `tested_against` and the prose, which is where a build note's toolchain belongs; the component offers no field for it. Also repair the frontmatter description, which read "speeds up a from-scratch build - large on compile-bound Chromium". That trailing clause has no subject to attach to, and the description is what search results and the field-note index show, so it is the one sentence that has to parse standing alone. Signed-off-by: Javier Tia <javier@peridio.com>
The drafting note pointed the engineer at a named local build workspace and at the internal tool used to capture the recordings. Both sit in the public docs repo from the moment the branch is pushed, and `draft: true` only keeps the page out of the published build - it does not keep the source out of the repo. The path also leaks internal repo naming for no reader benefit. The instruction does not depend on either detail: what the next person needs is which two runs to record and which numbers to lift off the timers, so say that and drop the rest. Signed-off-by: Javier Tia <javier@peridio.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft Field Note: a measurement-first look at where a compiler-cache cluster actually speeds up a Yocto build. Structured draft with
[ENGINEER:]placeholders, reviewed here on the PR (not merged) per the field-notes CONTRIBUTING.Angle (the honest spine)
[ENGINEER:]until the demo is recorded.Upstreaming
Ties the note's "what broke" to the public fixes we are landing on mozilla/sccache: RFC #2775 plus Wave-1 PRs #2776 and #2777, with later waves summarized.
Not ready to un-draft
draft: true(excluded from the production build); 11[ENGINEER:]placeholders remain.devtool demoChromium runs (one machine vs the cluster), confirm the cluster is clearly faster, fill the placeholders, embed the MP4s.Verification
yarn buildis not the gate for this change yet: the note isdraft: true, so Docusaurus excludes it from the production build. The MDX structure mirrors_template.mdxand the existing notes; full build validation applies when it is un-drafted.bakarreferences; no customer names (checked).Tracks ENG-2174.