Set CPU limit to 0.25 for the CI #369
Open
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
Current benchmarks consume a lot of CPUs mainly due to the checks done in K6 script. For a single CPU core allocated to Grafbase, I need roughly 7 others for K6 and 2-3 others for the subgraphs. So results are inaccurate as the machine is saturated. Cosmo is also likely impacted. On my machine setting the limit to 0.25 reduced total CPU usage to roughly 3 cores which would fit inside the CI machine.
Finistere
changed the title
|
@Finistere Not sure I understand the need for a change in CI? |
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.
Current benchmarks consume a lot of CPUs mainly due to the checks done in K6 script. For a single CPU core allocated to Grafbase, I need roughly 7 others for K6 and 2-3 others for the subgraphs. So results are inaccurate as the machine is saturated. Cosmo is also likely impacted.
On my machine setting the limit to 0.25 reduced total CPU usage to roughly 3 cores which would fit inside the CI machine.