Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Explain how monthly savings is computed in container request sizing. #1124

Merged
merged 3 commits into from
Sep 6, 2024
Merged

Explain how monthly savings is computed in container request sizing. #1124

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9fd2814
give insights into how monthly savings is computed for each container…
avrodrigues5 Sep 6, 2024
e233825
fix the space for 2nd indent
avrodrigues5 Sep 6, 2024
175fcbc
PR review addressed
avrodrigues5 Sep 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...ating-the-kubecost-ui/savings/container-request-right-sizing-recommendations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,14 @@ The container request right-sizing recommendations page shows a tabular view of

Recommendations from Kubecost can including both increasing, decreasing, as well as establishing net new resource requests. When Kubecost recommends a decrease in resource requests, this results in savings opportunities. The _EST. SAVINGS_ field (Estimated Savings) shows the estimated amount of monthly savings which can be achieved by adopting the recommendations. The amount of estimated savings depends on the Profile and other [configuration options](#configuring-request-right-sizing-recommendations) which are explained below. The container request right-sizing recommendations table is sorted by default in descending order according to the estimated savings available.

The request sizing algorithm calculates monthly savings estimates using CPU and RAM by comparing current costs with projected costs for the recommended resource allocation. Here's how it works:

1. The algorithm calculates the cost per CPU core and RAM Byte based on your current resource allocation during the analysis period.
2. The algorithm then gets the difference between your average CPU and RAM usage to the recommended amounts.
3. Finally, the algorithm multiplies the difference in resource usage by the calculated costs to estimate your monthly savings.

This approach allows Kubecost to provide accurate savings estimates tailored to your specific resource usage and costs. The overall monthly savings for all your containers are represented in the container request right-sizing recommendation page under estimated available savings.

The _CURRENT EFFICIENCY_ field shows the efficiency of the container as a result of its current usage-to-request ratio factoring in both CPU and memory. Efficiencies at or above 100% usually indicate the container is undersized in one or both resources and Kubecost recommends increasing requests.

Expand one of the rows to see more details on the workload and the recommendations offered by Kubecost. This view shows more information about the workload, including details such as the namespace and container name, along with the current request values and Kubecost's recommendations. The recommendations displayed in this view are also a result of the [configuration options](#configuring-request-right-sizing-recommendations) explained below.
Expand Down