diff options
| author | Pavel Zhukov <33721692+LeaveMyYard@users.noreply.github.com> | 2024-01-10 13:08:55 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-10 13:08:55 +0200 |
| commit | 76eeaeba5d5395cbf4c7ab968e2ef52ed523d4e8 (patch) | |
| tree | af8a50ba73ac89d2d8bca9aaaa83543af29c54d4 | |
| parent | acb4aa462a22684c744fa559d2311bd9ac3a8c54 (diff) | |
| parent | f95e259ed01bf098424cdd44652e98b96db27985 (diff) | |
Merge pull request #186 from alexis974/fix/readme-memory-buffer-percentage
Fix wrong memory buffer percentage in README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -339,7 +339,7 @@ By default, we use a _simple_ strategy to calculate resource recommendations. It - For CPU, we set a request at the 99th percentile with no limit. Meaning, in 99% of the cases, your CPU request will be sufficient. For the remaining 1%, we set no limit. This means your pod can burst and use any CPU available on the node - e.g. CPU that other pods requested but aren’t using right now. -- For memory, we take the maximum value over the past week and add a 5% buffer. +- For memory, we take the maximum value over the past week and add a 15% buffer. ### Prometheus connection |