ci: use larger runners for compilation-heavy jobs#4
Closed
huth-stacks wants to merge 1 commit into
Closed
Conversation
Switch nextest-archive, cargo-hack native-targets, and constants-check to ubuntu-latest-m (4 vCPU, 16GB RAM) for faster compilation. The release workflow already uses these runners. Expected ~30-50% faster compilation with negligible cost difference.
Owner
Author
|
Closing: ubuntu-latest-m runners are not available on personal fork accounts (requires GitHub Team/Enterprise org plan). This PR can only be validated on the upstream stacks-network org. The combined PR (#8) has been rebuilt without this change. |
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
1 participant
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.
What
Switch three compilation-heavy CI jobs from
ubuntu-latest(2 vCPU, 7GB RAM) toubuntu-latest-m(4 vCPU, 16GB RAM).Why
Rust compilation is CPU-bound and scales well with core count. These three jobs are the longest-running compilation tasks in the pipeline:
The release workflow (
github-release.yml) already usesubuntu-latest-m, confirming these runners are available to the org. Larger runners cost ~2x/min but complete in ~half the time, netting similar total cost.The Change
One word change in each of 3 files:
.github/workflows/create-cache.yml: nextest-archive jobruns-on: ubuntu-latest-m.github/workflows/cargo-hack-check.yml: native-targets jobruns-on: ubuntu-latest-m.github/workflows/constants-check.yml: check-consts jobruns-on: ubuntu-latest-m3 lines changed across 3 files. Other jobs in these files are untouched.
Metrics to Track
Security Checklist
Part of CI Optimization Series
PR 3 of 7. Expected impact: ~30-50% faster compilation on critical path jobs.