Update the utilisation guidance to avoid overutilisation #312
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
|
stefaniuk
force-pushed
the
alyo2-change-utilisation-guidance
branch
from
cb19c56 to
335bb46
Compare
|
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.
The Kingman formula tells you what happens when a resource has 100% utilisation, and it's not good:
Any system that has a latency constraint wants to be very careful about approaching 100% utilisation. I've reworded the advice here from aiming at 100% to aiming at 80%, which is a fairly safe amount of headroom.
This obviously doesn't apply to elastic on-demand infrastructure except where we are controlling autoscaling parameters.