Skip to content

Commit

Permalink
Revert to low cost fix (#5144)
Browse files Browse the repository at this point in the history 
* Update ocean-aks-cloud-cluster-overview.md

* Update ocean-aks-cloud-cluster-overview.md

* Update ocean-aks-cloud-cluster-overview.md

* Update ocean-aks-cloud-cluster-overview.md
  • Loading branch information
@rickshar
rickshar authored Dec 9, 2024
1 parent f9af05e commit f01ee26
Showing 1 changed file with 41 additions and 36 deletions.
77 changes: 41 additions & 36 deletions src/docs/ocean/ocean-aks-cloud-cluster-overview.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -61,16 +61,15 @@ To view these savings, click the **Bin Packing** tab (unless already displayed).

This tab displays:

* Number of Scaled-down nodes: If one or more nodes have been scaled down, click the link on the button to view details.
* Pie-chart - Virtual Node Group percentage breakdown for nodes.
* Pie-chart - Lifecycle percentage breakdown (regular, Savings Plans, Reserved Instances, and spots).
* Node Name.
* Virtual Node Group: You can click the link for a listed Virtual Node Group to display more details.
* Node Pool (name of node pool).
* VM Size: For example, standard_f4s
* Lifecycle: (regular, Savings Plans, Reserved Instances, and spots).
* Scale-Down Timestamp, for example, 06/25/2023 09:23:15

* Number of scaled-down nodes:
* Resource savings from bin packing in the following units:
* CPU resources saved in vCPU.
* Memory resources saved in GiB.
* GPU resources saved in GPU.


If one or more nodes have been scaled down, click the link on the **Node Scaled Down** button to view details in the Bin Packing window.

<details style="background:#f2f2f2; padding:6px; margin:10px 0px 0px 0px">

<summary markdown="span" style="color:#7632FE; font-weight:600" id=”texttolinkto”>View image...</summary>
Expand All @@ -79,51 +78,57 @@ This tab displays:

</details>

* Resource savings from bin packing in the following units:
* CPU resources saved in vCPU Hours.
* Memory resources saved in GiB Hours.
* GPU resources saved in GPU Hours.
* Number of scaled-down nodes.
* Pie-chart: Virtual node group percentage breakdown for nodes.
* Pie-chart: Lifecycle percentage breakdown (regular, Savings Plans, Reserved Instances, and spots).
* Node Name.
* Virtual Node Group: You can click the link for a listed virtual node group to display more details.
* Node Pool (name of node pool).
* VM Size: For example, standard_f4s
* Lifecycle: (regular, Savings Plans, Reserved Instances, and spots).
* Scale-Down Timestamp, for example, 06/25/2023 09:23:15

## Ocean Savings from Reverting to a Lower Cost Node Pool
## Ocean Savings from Reverting to Lower Cost Node Pools

This process is applied to nodes with compute resources that cannot be scaled down from the cluster's set of node pools. For example, suppose a pod was initially placed on a more expensive node due to resource constraints. In that case, Ocean Autoscaler can replace it with a less expensive node when it becomes available, consequently saving costs. This tab lets you see how much you save from this dynamic resource allocation.
This process searches for node pools that can be replaced with lower-cost node pools. For example, suppose a pod was initially placed on a more expensive node due to resource constraints. In that case, Ocean Autoscaler can replace it with a less expensive node when it becomes available, consequently saving costs. This tab lets you see how much you save from this dynamic resource allocation.

Ocean savings for reverting to a lower-cost node pool are calculated from the difference in price between the old node and the new node. For more information, see [Revert to Lower Cost](https://docs.spot.io/ocean/features/revert-to-lower-cost-node?id=revert-to-lower-cost-node) Node pool.
Ocean savings for reverting to a lower-cost node pool are calculated from the difference in price between the old scaled-down nodes from the specific node pool and the new scaled-up nodes, which are assumed to be related to several different node pools. For more information, see [Revert to Lower Cost](https://docs.spot.io/ocean/features/revert-to-lower-cost-node?id=revert-to-lower-cost-node) Node pool.

To view these savings, click the **Revert to Lower Cost** tab (unless already displayed).

![aks-rev-to-lower-cost](https://github.com/user-attachments/assets/d6dd4598-7e9e-4348-a98a-e68fb0fdd478)

This tab displays:

* Nodes reverted to lower cost: If one or more nodes have been reverted to lower cost, the number of reverted nodes appears. Click to view the number of nodes reverted to lower cost in the selected time range in the Revert to Lower Cost window. View the types and costs of the nodes, etc).
* Nodes reverted to lower cost:
* Resource savings from reverting to lower cost in the following units:
* CPU resources saved in vCPU.
* Memory resources saved in GiB.
* GPU resources saved in GPU.

* Avg. percentage hourly cost saved: Avg. percentage cost reduction from reverting to the new VM type [SUM (% hourly cost saved)].
If one or more nodes have been reverted to lower cost, the number of reverted nodes appears.
Click **Revert to Lower Cost** to view the number of nodes reverted to lower cost in the selected time range in the Revert to Lower Cost window.

* Pie chart - Virtual Node Group percentage breakdown for nodes.

List showing replacement information: an entry for each reverted node is listed with these details:

* Node pools for the original and reverted nodes.
* Number nodes in the old and new node pools.
* Hourly cost of the original and reverted nodes. Displays the total cost of all nodes in the same node pool: [nodes count * hourly cost].
* Hourly cost saved as a percentage: Cost reduction from converting to the new VM type: [old hourly cost - SUM (new hourly cost) * 100].
* The Virtual Node Group's name (click the link for a listed VNG to display your custom VNG details).
* Scale-down timestamp in format MM/DD/YYYY HH: MM: SS

<details style="background:#f2f2f2; padding:6px; margin:10px 0px 0px 0px">
<details style="background:#f2f2f2; padding:6px; margin:10px 0px 0px 0px">

<summary markdown="span" style="color:#7632FE; font-weight:600" id=”texttolinkto”>View image...</summary>

<img width="1000" src="https://github.com/user-attachments/assets/943bed5d-2bd8-49cb-9972-aa2de5a0f563" />

</details>

* Resource savings from reverting to lower cost in the following units:
* CPU resources saved in vCPU Hours.
* Memory resources saved in GiB Hours.
* GPU resources saved in GPU Hours.

* Number of nodes reverted to lower cost.
* Avg. percentage hourly cost saved: Avg. percentage cost reduction from reverting to the new VM type [[SUM(old hourly cost) - SUM (new hourly cost)]/[SUM(old hourly cost)] * 100].
* Pie chart - Virtual Node Group percentage breakdown.
* List showing replacement information: an entry for each reverted node pool is listed with these details:

* Node pools of the scaled-down and scaled-up nodes.
* Number of scaled-down and scaled-up nodes.
* Hourly cost of the scaled-down and scaled-up nodes. Displays the total cost of all nodes in the same node pool: [nodes count * hourly price].
* Hourly cost saved as a percentage: % Cost reduction from converting to all the new VM type: [[SUM(old hourly cost)- SUM (new hourly cost)]/[SUM(old hourly cost) ]*100]
* The Virtual Node Group's name (click the link for a listed VNG to display your custom VNG details).
* Scale-down timestamp in format MM/DD/YYYY HH: MM: SS

## Ocean Managed Nodes and Resources Panel

<img width="1000" src="https://github.com/user-attachments/assets/065b7f12-769a-4e46-9900-7b17fb81553d" >
Expand Down

0 comments on commit f01ee26

Please sign in to comment.