Add scale out experiment scenario #128
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
This helps in automating multiple experiment runs.
Multiple `nodeSelectorTerms` are ORed. Guarantee scheduling to high-cpu worker pool.
Schedule kube-controller-manager to high-cpu worker pool as well.
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.
What this PR does / why we need it:
This PR adds a second experiment scenario:
scale-out.The new scenario has a high churn rate and is designed to overload 5 webhosting-operator instances with 5 workers.
It is executed for 1 to 5 instances each. For every instance count, the maximum load capacity is calculated where the SLOs are still satisfied.
To make the high churn rate work, several things need to be improved:
GOMAXPROCSto match CPU quota (prevents CPU throttling and decreases tail latency)