ci(memory): widen test_memory_json_churn RSS budget for #1090 GC rework - #1286
Merged
Conversation
Ubuntu CI on tag v0.5.1019 (run 26236443275) had 3 of 4 GC modes blow the existing 250 MB / 275 MB ceilings on test_memory_json_churn: default 268 MB / limit 250 MB (+7%) gen-gc-explicit 268 MB / limit 250 MB (+7%) mark-sweep 114 MB / limit 250 MB (OK) force-evac+verify 290 MB / limit 275 MB (+5%) Locally on macOS arm64 (2026-05-21, /usr/bin/time -l on M-series): default 241 MB mark-sweep 91 MB force-evac+verify 263 MB All within budget. The consistent ~28 MB Linux-over-macOS gap is the same Linux glibc allocator + RSS-accounting shape that prompted Ralph's prior 200→250 bump in f95ef05. The remaining drift is GC-rework working-set that #1090 ("GC roadmap: make minor GC structurally cheap") will reclaim once it lands. Bumping to 290 / 315 (~8% headroom over current observed values) gets CI green and unblocks releases while #1090 is in flight. Comment on the run_test call points future-us at the issue so the limit gets tightened when the rework closes. Refs #1090.
This was referenced May 21, 2026
proggeramlug
added a commit
that referenced
this pull request
May 22, 2026
…1422) PR #1324 ("Port GC checkpoint runtime work for #1090", e933b89) reverted the 290/315 MB ceiling from v0.5.1022 (#1286 / 4fcfddb) back to 250/275 while rewriting the surrounding comments. The v0.5.1024 release-packages compile-smoke job then hit the same Ubuntu overrun we already fixed once: default 268 MB / limit 250 MB (+7%) gen-gc-explicit 268 MB / limit 250 MB (+7%) force-evac+verify 288 MB / limit 275 MB (+5%) Restore the wider ceiling and replace the comment with one that references the actual rebump history (v0.5.1024 measurements + the #1324 revert) so the next contributor doesn't accidentally undo it again. Production binaries are stripped by the linker; these RSS figures are unstripped release-build artefacts used as a regression signal, not a deployment-size measurement. Refs #1090 #1286 #1324.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
test_memory_json_churnRSS-over-limit failures in 3 of 4 GC modes (default 268, gen-gc 268, force-evac+verify 290) against the 250/275 MB ceilings.f95ef059(200 → 250).GC roadmap: make minor GC structurally cheap); revisit the ceilings when that closes.Test plan
cargo fmt --all -- --checkcleanscripts/run_memory_stability_tests.shtouched)