This website uses cookies to ensure you get the best experience.
Learn more.
A stateless service has variable demand and should scale around average CPU utilization of 55%. The team does not want to maintain several manual threshold steps. Which policy is appropriate?
Published
- A target-tracking policy on a suitable average CPU utilization metric with a target of 55%.
- A dashboard with no scaling action or capacity controller.
- A fixed capacity change once each year without observing demand.
- A policy using cumulative lifetime CPU time as if it were average utilization.
Comments — 0
Sign in to comment