The samples.csv row of an interval that touches the start of a freeze
now gets the window of its unfrozen part, as the window aggregates do
since the thaw correction. CPU per successful request is no longer
computed for a container absent from the window. The definitions in
the summary describe which intervals the window maximum covers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A sample interval that crosses docker pause or unpause carried the CPU
spent before the pause and the burst after unpause into the failover
window by proportional split. Use the pause and unpause moments from
Docker events so that interval CPU lands outside the frozen span.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Run bench/sampler.sh in a new scan mode (cgroup walk, no network, no
psql or LB polling) for the whole load of the failover and rollout
profiles. bench/resources.py turns the samples into per-window CPU,
throttling and memory of every component and the VM, with
samples.csv, resources.csv and summary sections; CPU per successful
request only in steady windows. Check the peak CPU budget before the
stand starts.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>