Optimize CircleCI builds with a mix of xlarge and large VMs
#32174
Conversation
This file contains 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
rsimha
changed the title
xlarge and large VMs
kristoferbaxter
approved these changes
Jan 25, 2021
PetrBlaha
pushed a commit
to PetrBlaha/amphtml
that referenced
this pull request
Jan 28, 2021
…roject#32174) * Compare CircleCI build time between xlarge and large * Use `xlarge` for builds, `large` for tests
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.
We currently use
xlargeCircleCI VMs, which give us a build round trip time of under 20 mins. E.g. this build.From the pricing chart,
xlargeVMs cost 5x as much per minute aslargeVMs.This PR optimizes the price / performance of CircleCI builds by using
xlargeVMs for jobs that build the AMP runtime (highly parallelized), andlargeVMs for all other jobs that run tests (mostly done serially).