-
Notifications
You must be signed in to change notification settings - Fork 81
add cpu provisioning docs #430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: CPU provisioning | ||
description: Learn how to set the CPU provisioning | ||
ratio. | ||
--- | ||
|
||
Coder allows you to set the CPU provisioning ratio for each of your | ||
organizations. The CPU provisioning ratio configures workspaces with a | ||
guaranteed minimum capacity, while enabling them to use available capacity for | ||
improved performance. The guaranteed minimum capacity is equivalent to the total | ||
CPUs provisioned for a workspace divided by the provisioning ratio. | ||
|
||
For example, let's say that you set a CPU provisioning ratio of 8:1. If a user | ||
creates a workspace with 4 CPUs, then Coder will reserve 0.5 CPUs on the | ||
underlying node, with a maximum limit of 4 CPUs. | ||
|
||
## Changing the CPU provisioning ratio | ||
|
||
1. Go to **Manage** > **Organizations** and select your organization. | ||
1. At the top of your organization page, click **Actions** > **Edit**. Scroll | ||
down to **CPU Provisioning Rate** and set the maximum ratio. | ||
1. Click **Update**. | ||
|
||
 |
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reminds me that we should think about whether we want to keep using the term provisioning and overprovisioning... I don't think it's common usage of the term. I understand the need to document what we currently have, though, so this is a good improvement, thank you!