+8
−29
Loading
MEMORY_MADV and MEMORY_HOT_MB existed so the decommit policy could be gauged against a real workload without rebuilding. That happened: production simulations put the policy at nearly no cost against plain retention while returning the hoard, and the branch was asked to land in this shape. So the policy becomes what 56fccba2 said it would if it survived - MADV_DONTNEED and a 4 MiB hot window as compile-time constants, no environment surface. Anyone still A/B-ing with the env vars: pin b447515e, the last commit that has them. go test passes with and without -tags=memory.counters, go vet -unsafeptr=false and staticcheck are clean, and all supported targets cross-build. Co-Authored-By:Claude Fable 5 <noreply@anthropic.com>