You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: correct the computation of the percentage differences and stats
Fix the computation of the CPU/Memory difference columns to express
the result as the increase/decrease of the request in terms of the
recommendation.
Print the memory recommendation quantity using the same scale as the
request in a human-friendly format.
Scale the statistics values to the number of replicas requested in
the spec of each controller.
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,10 @@ It creates a single binary file for the host machine platform/architecture in th
43
43
44
44
## Usage
45
45
46
+
### How to interpret the output?
47
+
48
+
The columns `% CPU DIFF` and `% MEMORY DIFF` represents the percentage of increase/decrease for the request in terms of the recommendation. For example, if the request is 4 CPU (4000m), and the recommendation is only 1 CPU (1000m), the difference is +300%. As a rule of thumb, you can think of positive values as "overcommitment" and negative values as "under commitment".
49
+
46
50
### Demo
47
51
48
52
The following examples were produced from a brand-new Kubernetes cluster created with [`k3d`](https://k3d.io/v5.2.2/). The `VerticalPodAutoscaler` resources were automatically created by the [`goldilocks`](https://github.com/FairwindsOps/goldilocks) operator.
0 commit comments