Autoscaling Controller · View 31 of 37 · 5 · Operations
The decision
- Cost of stability — capacity retained by dead bands, sustain windows, scale-in rate limits and cooldowns — is reported in currency per day.
- That makes the latency-versus-cost trade visible rather than implicit, and it is the number the policy is tuned against.
- Warm-pool cost is accounted separately from serving cost, so a pool cannot hide inside a target's bill.
Budgets
- Declared monthly spend budget per target. As it is approached the controller raises scale-in aggressiveness inside safety bounds and alerts rather than breaching min.
- Controller's own infrastructure under 1.5% of managed fleet compute spend.
Risks
- Budget-driven aggressiveness is the one place cost is allowed to influence capacity. It is bounded by min and by the safety bounds, and every such adjustment is journalled with its reason.
