clm-0001
measured-herelow ●○○
citable URL: https://halobench.com/records/clm-0001/ — this address never moves; the anchor /records/#clm-0001 keeps resolving
Static pool utilisation did not predict the 2026-07-21 OOM. The box crashed at 83.8% estimated utilisation, and cfg-0002 sits at that same 83.8% today.
verified 2026-08-03 · volatility medium
evidence inc-0004
Note — the record's own working
total_gb is weights + KV + a fixed overhead — a static estimate. What actually exhausted memory was runtime growth: context checkpoints defaulting to 32, cache-ram, and fragmentation. None of it appears in the record. The mitigations worked precisely because they targeted dynamic growth (checkpoints capped at 4, desktop stack removed, swap raised to 16G) — which is why they moved the ratio not at all. Until observed_peak_gb is collected from telemetry, the 0.8 warn line is a threshold on a number that has never predicted an OOM. Falsifiable: collect peak RSS/GTT under load and compare against the estimate.