chore(ci): right-size acceptance executors - #7010
Open
parker-snyk wants to merge 2 commits into
Open
Conversation
Use Large executors for the x86, ARM, and Alpine acceptance suites after paired CircleCI runs stayed within the 10% wall-time threshold and reduced credit usage. Keep Windows on Large because the Medium experiment exceeded the threshold. Build jobs, acceptance sharding, and test commands remain unchanged.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
parker-snyk
marked this pull request as ready for review
July 17, 2026 15:03
This comment has been minimized.
This comment has been minimized.
1 similar comment
PR Reviewer Guide 🔍
|
Contributor
parker-snyk
commented
Jul 17, 2026
| docker: | ||
| - image: alpine:3.23 | ||
| resource_class: large | ||
| alpine-arm64: |
Contributor
Author
There was a problem hiding this comment.
Should we also change alpine-arm64 to be alpine-arm64-xlarge to make it more clear on the size?
PeterSchafer
approved these changes
Jul 20, 2026
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
2 participants
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.
Several acceptance jobs were still using eight-core executors. This PR moves four acceptance jobs from xlarge to large executors:
CircleCI already splits the acceptance files across parallel containers. Inside each container, the acceptance command runs
npx jest --maxWorkers=1, so each shard executes one Jest worker at a time. The xlarge executors provide eight cores to each shard, but Jest cannot spread that shard's tests across them. Historical usage reflected this, with median CPU around 11% to 12% and median RAM around 4%. Moving these jobs to Large removes idle capacity without reducing the existing shard-level parallelism.I tested other executor combinations, but they did not improve the result within the agreed runtime threshold. This PR only contains the configuration that met that threshold. The build jobs, shard counts, test selection, and Remote Docker behavior are unchanged.
The small speed difference is likely normal CI variation. Both retained-configuration runs completed within the baseline runtime, so we did not observe any time degradation while full-workflow credits fell by 21.9% to 24.8%.
Validation also included
make format,make lint, andmake build.Tracking: IDP-7