chore: Add information re: cluster sizing reqs #390
Merged
Conversation
This file contains hidden or 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
|
✨ Coder.com for PR #390 deployed! It will be updated on every commit.
|
khorne3
approved these changes
Jun 7, 2021
ammario
reviewed
Jun 8, 2021
| We also recommend [monitoring](../guides/admin/usage-monitoring.md) your usage | ||
| to determine whether you should change your resource allocation. Accepting a | ||
| peak utilization of RAM of around 50% and CPU of around 70% is a good way to | ||
| balance performance with cost. |
There was a problem hiding this comment.
"peak utilization" is poorly defined so this last sentence may confuse people more than help. I'd recommend dropping it. The rest looks good to me.
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 PR attempts to add some additional recommendations around sizing. A common ask of our customers is what size of a node (and how many nodes) they should have in their cluster for
xnumber of developers.This is very difficult to determine, as the work a developer is doing within their environment can vary greatly, requiring a different amount of resources. This PR addresses that with giving recommendations of initial sizing + measuring and iterating to right size it over time.
[ch13598]
@khorne3 I continued the "quote" block we had here, but the design of that may look weird with so much text in a "quote" block. Let me know if you'd like that pulled out into normal text or something else. 👍 See below screenshot of the large quote block: