v0.32.5 — Reservations shrink after a peak on a busy queue

Busy queues no longer hold a finished peak for the rest of a job. Pressure checks, headroom and safety margins are unchanged.

Fix

• Reservations shrink after a peak again, even when many jobs are waiting. memcap reserves a running job's recent peak and lets it drop after 60 seconds of steady lower usage. With several jobs waiting, observations often arrived a fraction of a second out of order. memcap mistook that for a gap in measurement and kept the job's lifetime peak reserved until it finished. On October 27, a Go test run that peaked at 4.5 GiB kept 5.6 GiB reserved for eight minutes while using 0.25 GiB, so 15 jobs waited while memory pressure was green. Out-of-order observations now count toward the window. They can raise a reservation but never lower it early. Real measurement gaps still hold the reservation.

Upgrade

brew upgrade memcap

Jobs that are already running keep their current reservations until they finish. New jobs use v0.32.5.

Full details: CHANGELOG.md