Knowledge base
Read current, direction, then proposed.
A CPU request is a scheduling reservation. Read the current provider observation separately from the historical assessment. A lower proposed request is an analytical direction, not proof of monetary savings.
Inspect the evidence and protected demand, plus any HPA coupling or other material condition. An assessment that cannot support an actionable proposal should withhold the recommendation.
Back to Knowledge BaseOne Problem at a Time · Episode 1 · 1:15
Why requests and usage differ, and why a low average alone cannot justify a reduction.
Illustrative numbers, not a customer result or savings claim. Requests affect scheduler placement; existing containers can still use otherwise idle CPU. In the CPU example, observed peaks are based on sampled five-minute averages. Seven days is the reduction-history gate described here; protective memory increases can follow a different path.
English captions are burned into the video. An optional English caption track and transcript are also available. Use fullscreen for small screen details.