ci: benchmark CircleCI M4 Pro Large - #239
Closed
kyleve wants to merge 1 commit into
Closed
Conversation
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
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.
Summary
m4pro.largem4pro.mediumbaseline from ci: migrate iOS tests to CircleCI M4 Pro #237Why
CircleCI's Large worker doubles the managed macOS allocation from 6 CPUs / 28 GB to 12 CPUs / 56 GB, while also doubling compute price from 200 to 400 credits per minute. This PR isolates that resource-class change so its CI run can show whether the added parallelism improves elapsed time enough to justify the cost.
Review focus
This is a temporary benchmark PR and changes only the shared CircleCI executor's resource class. It is not intended to merge until the measured timing and cost trade-off are reviewed.
Testing
circleci config validate .circleci/config.ymlcircleci config process .circleci/config.ymlgit diff --check