Commit graph

5 commits

Author SHA1 Message Date
trvon
c60b44fb4d
kpi: budget the per-phase RSS peak, not only the last sample
compare() budgeted daemon_rss_last_mb only, so a regression that spiked and
then settled passed: the peak was printed but never checked, leaving just the
absolute 512 MB ceiling. Both metrics are now budgeted per phase through one
helper — max(32 MB, 15% of the baseline) for the phase-end value and
max(64 MB, 15%) for the peak.

The 64 MB floor is measured, not chosen: with a shared 32 MB floor three
same-version repeat pairs (8-r1->8-r2 idle peak +59.6 MB, 9-r1->9-r2 storm
+36.3 MB, 9-r1->9-r3 +36.0 MB) would be called regressions, because a single
transient sample spreads about twice as wide as the phase-end value. 64 MB
clears all nine same-version pairs while every v0.2.8 -> v0.2.9 pair still
trips it; re-checked four same-version pairs here with zero over-budget phases.

The peak check adds real signal: on the stored runs it catches v0.2.9's idle
peak at +137.4 MB where the last-sample check saw +102.4 MB. Missing samples
still fail closed and never read as "no growth".
2026-11-19 16:19:41 -07:00
trvon
ed59a0ee26
kpi: gate on daemon RSS, not just container memory
The constrained-lane report gated idle CPU, exec-decision p95 and dropped
events, so a real memory regression could pass unnoticed — v0.2.9 grew daemon
RSS by 132-141 MiB against v0.2.8 in all three interleaved pairs.

Each phase now reports daemon RSS (max, last, sample count) from the existing
status.jsonl resources.rss_mb samples, with container memory kept as a
secondary metric, and reports fail closed when daemon RSS samples are missing
rather than silently skipping the check. --compare prints a per-phase delta
column against a baseline-relative budget of max(32 MB, 15% of the baseline)
and exits non-zero with OVER BUDGET lines, so a regression is visible instead
of buried in container statistics that also include the harness.

Measured on the stored runs: the v0.2.8 -> v0.2.9 pairs breach the budget in
all six phases (+87.2 to +141.0 MB), while a same-version pair does not (worst
spread +29.1 MB). The docstring states exactly what a non-zero exit covers.
2026-11-17 13:45:17 -07:00
trvon
a5f2dbedfc
KPI: bound collection and reject incomplete measurements
Use suspend-aware BOOTTIME waits and owned-container cleanup without changing the workload. Reject missing coverage and preserve producer/report failures. Include runtime/helper regressions, constrained build-job support and live exec-guard crash safety. Document the failed live/idle gates without relaxing thresholds or claiming production acceptance.
2026-11-03 06:57:00 -07:00
trvon
4ca4b5c8a8
Measure the evidence write path in the KPI
A detect phase runs 40 distinct binaries carrying a KPI-only YARA marker,
then repeats them, so db_commit and correlation are timed (the earlier
workload never produced a detection).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 06:43:45 -06:00
trvon
2d5e05e8db
Add resource governor, scan profiles and KPI harness
PSI/cgroup-aware governor with efficient/balanced/aggressive profiles,
background pacing and thread priorities; timing histograms and optional
Tracy zones; a capped Docker KPI harness with report/compare tooling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 18:17:16 -06:00