Bring standalone infraternal agent RSS below 15 MiB #88
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and evidence
The standalone normal release process measured 15.465 MiB RSS in its final quiet sample against the 15 MiB limit. With 612 fixtures it measured 18.684 MiB. The formal gate separately measured 15,925,248 bytes (15.188 MiB). The quiet sample split was 12.699 MiB file-backed and 2.766 MiB anonymous. The related 60-second idle measurement ran at load1 6.43–9.61; RSS was taken in the quiet process state. Evidence is in idle-summary.json and the gate output in audit-results.json.
The standalone runtime already limits this path to two workers and disables transparent huge pages (crates/infraternal/src/main.rs:246-260), so repeating the worker-count change is not an RSS optimization.
Recommendation
Trace resident code/shared initialization and inventory retention, then reduce measured resident state. Do not assume a binary-size reduction lowers RSS; avoid allocator tuning without attribution. Define the warm/cold inventory occupancy used for comparisons in the separate budget-definition issue.
Payoff, effort and risk
Expected gain: save at least 0.465 MiB at quiet baseline and pass the existing 15 MiB standalone infraternal agent cap. The 612-fixture result should be reported separately with resource count.
Quick win vs deeper change: classify file-backed and anonymous resident pages in ≤1 day; an attributed code/initialization/inventory change is estimated at 1–3 days.
Risk: medium; residency depends on initialization and resource state, and optimization must not discard shared or required inventory.
Priority: Next milestone.
2026-10-04 owner decisions: The owner explicitly set the infraternal agent RSS budget from this audit. Keep the 15 MiB cap and make each comparison's resource occupancy explicit. One-binary shipping remains settled. Related: #66 for disabled provider work.
Report: perf-audit report
Source: perf-audit 2026-10-04