Skip to content

TEMPORARY, do not merge: measure the Hermes image's push two ways (FIN-360 follow-up) - #925

Closed
futurepaul wants to merge 2 commits into
masterfrom
claude/measure-image-push
Closed

futurepaul wants to merge 2 commits into
masterfrom
claude/measure-image-push

Conversation

@futurepaul

Copy link
Copy Markdown
Collaborator

A measurement for FIN-360's follow-up, never to merge: docker build --load + docker push against docker buildx build --push from BuildKit's builder, both to a registry on the runner, timed with the disk measured. Closed once read.

🤖 Generated with Claude Code

futurepaul and others added 2 commits October 31, 2026 22:27
The merge queue's preview-image prebuild died twice in `cargo xtask image
preview --queue` with no conclusion (runs 41265350002, 41266642000): its
runner's own worker log says "No space left on device". The Hermes image
is held twice there, in BuildKit's container builder and, after
`docker build --load`, in Docker's own store, with its build cache: on an
ubuntu-24.04 runner with a 72 GB root (about 12 GB free) that fills the
disk, as it did the Docker lane's (#890).

#890's step becomes an action (.github/actions/free-disk): the runner's
Android, .NET, Haskell, Swift and CodeQL and its cached Docker images go,
28 GB, and the disk's and the memory's use is sampled every 5 seconds.
The queue's prebuild and master's preview-image job run it once their
probe says they build, the Docker lane as before, and each says its peaks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rom BuildKit (FIN-360's follow-up)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@futurepaul

Copy link
Copy Markdown
Collaborator Author

Read: on a 145 GB ubuntu-24.04 runner, with the builder warmed as the prebuild's is (BuildKit holding 14.0 GB), A (docker build --load + docker push) took 44 + 9 = 53 s and +7.1 GiB of disk (Docker's 5.9 GB copy and the local registry); B (docker buildx build --push from BuildKit) took 9 s and +1.4 GiB (the local registry alone). The cut follows in its own PR.

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