Headroom reduction workload optimization

This topic describes optimizing a workload with Headroom reduction.

A workload is optimized after the following steps:

1. You apply Headroom reduction to a workload together with a minimum replica optimization strategy. The strategies are based on the expected reduction in application start times together with historical data collected by the Insights agent.

2. Kompass prepares and hibernates nodes to protect the workload.
   When those are ready, Kompass reduces the workload minimum replicas according to the selected optimization strategy.

   This process completes within an hour of applying the solution.

   You can apply and manage Headroom reduction from the Zesty platform user interface or using CLI.

You can choose from the following minimum replica optimization strategies:

After the initial reduction in minimum replicas, Kompass continues to analyze and adjust - if needed - the minimum replica setting to ensure that managed workloads are being optimized according to the selected strategy. Changes are made when a change in the usage pattern is determined or when an optimization strategy is changed.

You can apply Headroom reduction to a workload using the user interface or using YAML.

After Headroom reduction is active on a workload, you can see the impact on the workload in terms of CPU, RAM, cost, and other metrics in the user interface. You can also change the selected optimization strategy or remove the solution entirely. For more info, see Apply and manage Headroom reduction

For information about supported environments and limitations, see Compute solution supported environments and limitations.

See also:

• How Headroom reduction works

• HiberScale technology

• Apply and manage Headroom reduction