ci: lower CPU requests and allocate 1.5G per CPU #3121
Merged
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
|
Let's do coreos/coreos-ci-lib#118 first. |
This roughly matches what we do now in e.g. the FCOS pipeline and a few other places. Otherwise, we may hit against our memory limit and get evicted. See coreos#3118 for more background info.
jlebon
force-pushed
the
pr/ci-adjust-requests
branch
from
41d64cd to
71ea89c
Compare
|
I think the effect of this is us requesting less memory than we did before. Was that intentional? |
|
Yes. It's 1G of RAM less, but also 2 CPUs less which means 2 less tests in parallel (i.e. between 2G and 3G less peak RAM usage). |
|
Restarted CI now that coreos/coreos-ci-lib#118 is in. Let's see what happens! |
|
LGTM also |
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.
This roughly matches what we do now in e.g. the FCOS pipeline and a few other places. Otherwise, we may hit against our memory limit and get evicted.
See #3118 for more background info.