-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Rewriting markdown file of reasonable CPU and memory requests
- Loading branch information
1 parent
a730976
commit 1d229a8
Showing
3 changed files
with
54 additions
and
33 deletions.
There are no files selected for viewing
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,11 @@ | ||
### Confirmation | ||
I *confirm* that the `requested CPU` resources are reasonable to avoid overcommitment of resources and optimize scheduling of workload resources. | ||
I *confirm* that the requested CPU resources are reasonable to avoid overcommitment of resources and optimize the scheduling of workload resources. | ||
|
||
## What's the Risk? | ||
Requesting a reasonable amount of CPU might be difficult and is always a tradeoff. | ||
Setting the requested CPU too low may lead to starvation and the container not getting needed CPU cycles. | ||
Setting the requested CPU too high may lead to inefficiency and extra CPUs. | ||
In addition, the value may depend on the criticality of your Kubernetes resources. | ||
|
||
## How to Identify Proper Values? | ||
Historical data are a good indicator of what your Kubernetes resource needs. For instance, check the 99th percentile of the last 24 hours and add some extra headroom depending on the criticality of your Kubernetes resources. | ||
If you don't have historical data, a load test may help you to generate more insights. |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
I *confirm* that the requested memory resources are reasonable to avoid overcommitment of resources and optimize the scheduling of workload resources. | ||
|
||
## What's the Risk? | ||
Requesting a reasonable amount of memory might be difficult and is always a tradeoff. | ||
Setting the requested memory too low may lead to Kubernetes killing the container. | ||
Setting the requested memory too high may lead to inefficiency and extra memory. | ||
In addition, the value may depend on the criticality of your Kubernetes resources. | ||
|
||
## How to Identify Proper Values? | ||
Historical data are a good indicator of what your Kubernetes resource needs. For instance, check the 99th percentile of the last 24 hours and add some extra headroom depending on the criticality of your Kubernetes resources. | ||
If you don't have historical data, a load test may help you to generate more insights. |