Transit wants to rightsize GIS worker requests after observing that pods request far more CPU than they use in steady state. What comparison guides that decision?
Select an answer to reveal the explanation.
Short Explanation
Rightsizing is matching the lunch order to what people actually eat—stack requests next to real usage from top/metrics, then trim the waste or bump the shortfalls.
Full Explanation
Effective capacity planning compares configured requests (and limits) against observed utilization from the metrics pipeline. Persistently high requests versus low usage indicate over-requesting that wastes schedulable capacity; the opposite suggests under-requesting risk. Blindly equating requests to full node CPU, ignoring metrics, or deleting requests does not produce sound rightsizing.