Skip to content

Add 16- and 32-core sample runners for Chroma and Zed - #95

Merged
gauravtiwari merged 1 commit into
mainfrom
claude/upstream-shape-sample-runners
Nov 13, 2026
Merged

gauravtiwari merged 1 commit into
mainfrom
claude/upstream-shape-sample-runners

Conversation

@gauravtiwari

Copy link
Copy Markdown
Contributor

Summary

Chroma's upstream image build runs on blacksmith-16vcpu-ubuntu-2404 and Zed's release build on a Namespace 32x64 profile. The largest sample runners here were 8 cores, so a manual sample could not use the machine size upstream uses.

This adds four runner entries and allows them on the existing sample lanes:

Runner key Label Used by
blacksmith-16 blacksmith-16vcpu-ubuntu-2404 blacksmith-builder, boringcache-docker-plus-reader
namespace-16x32 nscloud-ubuntu-24.04-amd64-16x32 boringcache-cargo-plus-reader
namespace-32x64 nscloud-ubuntu-24.04-amd64-32x64 boringcache-cargo-plus-reader
namespace-32x64-cache nscloud-ubuntu-24.04-amd64-32x64-with-cache, with its own cache tag namespace-cache

No case's [runs] or [samples] changes, so rolling runs and the weekly samples are unaffected. The new runners are selected with -f runner= on a manual sample.

Limits

  • The Namespace 32x64 cache volume uses a new cache tag and starts empty. Its first sample is a cold build for that lane and is not a comparison.
  • The existing BoringCache runners on Namespace use account profiles, one with swap configured. The new ones use plain shape labels. Matching core count does not establish matching memory or swap.
  • Preflight does not cover these runners: reader lanes are excluded from fresh and preflight matrices, and adding the runners to [runs] would put them in rolling. The first sample dispatch from main is the first time the labels are exercised.

Runner labels

Checks

Not run locally: the repository needs Ruby 4.0.7 and the machine this was written on has 3.3.6. The TOML parses and every lane's runner key exists in runners.toml. The Check workflow on this pull request runs the tests, bin/bench check and actionlint.


Generated by Claude Code

Chroma's upstream image build runs on blacksmith-16vcpu-ubuntu-2404 and
Zed's release build on a Namespace 32x64 profile. The largest sample
runners here were 8 cores, so a manual sample could not use the machine
size upstream uses.

Add blacksmith-16, namespace-16x32, namespace-32x64 and
namespace-32x64-cache, and allow them on the existing sample lanes. No
case's [runs] or [samples] changes, so rolling and weekly samples are
unaffected; the new runners are selected with -f runner=.

Runner labels:
https://docs.blacksmith.sh/blacksmith-runners/overview
https://namespace.so/docs/reference/github-actions/runner-configuration
@gauravtiwari
gauravtiwari merged commit 3e9264c into main Nov 13, 2026
5 checks passed
@gauravtiwari
gauravtiwari deleted the claude/upstream-shape-sample-runners branch November 13, 2026 12:26
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.

2 participants