chadtmiller.com/knotless
git that lives in your Atmosphere account
1
10
The runner host runs three jobs, on a dedicated AX41
Closedchadtmiller.com added 1 commit
Approved
This raises the runner host from two jobs to three (KNOTLESS_RUNNER_JOBS and --pull-jobs) in deploy.yml and the README, and it replaces the "Grow: rescale to CX53" note with a "Move" procedure. The numbers hold up. Three jobs of 4 CPUs and 7 GiB come to 12 CPUs and 21 GiB, which fits 12 threads and 64 GB. --pull-jobs 3 matches --jobs 3, and the code accepts it (pull_share is capped at 4).
Some README text is now stale. None of it should hold the pull:
- Near line 186, "cargo would still start a rustc for each of the host's 8 cores" no longer fits the 12-thread host.
- The "Setting it up" step still orders a CX43 (8 vCPU, 16 GB).
- The "Limits" bullet still says "2 of the 4 jobs".
I didn't check the Move steps against setup.sh or deploy.sh. They are prose I can't verify from the diff.
What changes
The runner host runs three jobs of 4 CPUs and 7 GiB rather than two, as it has moved from a cx43 to a dedicated AX41 (6 cores, 12 threads, 64 GB). Its README says so, and how to move a runner host, in place of rescaling to a CX53.
Why
The cx53 it was to be resized to has been out of stock in every location for days. Memory is what held it to two jobs. Each deploy of main writes these settings to the host, so without this one the next deploy would put it back to two.
How it was checked
The AX41 runs these settings now, through
deploy/runner-host/deploy.sh:setup.sh's checks passed, the runner is picking up runs, and the bot login answers over HTTPS. This pull's own checks run on it.Shortcomings
Its caches started empty, so first runs build in full. How much faster it is than the cx43 is not measured yet, and the cx43 is kept, stopped, until it is.
🤖 Generated with Claude Code