feat(cli): support flattened builds - #8724
Draft
Parker J. Rule (pjrule) wants to merge 13 commits into
Draft
Conversation
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.
Summary
Expected impact
In the Kubernetes BuildKit benchmark, combining the generated Python user steps into one non-empty filesystem layer reduced median C3 + gVisor solve time by about 10 seconds (54.93s to 44.76s). Fast samples showed roughly 20–24 seconds of structural savings. Compressed image size was effectively unchanged; the gain came from avoiding repeated native-snapshot copies.
This deliberately trades fine-grained warm-cache reuse for faster cold, short-lived builders.
Validation