test(benchmarks): automatic peak-memory-vs-native column#201
Merged
NathanFlurry merged 1 commit intoJul 2, 2026
Merged
Conversation
Every latency-matrix op now reports peak memory attributable to the work, per lane, plus memTax = guestPeak/nativePeak: - guest/wasm/vmCmd lanes: sidecar peak above the prewarmed baseline — write 5 to /proc/<sidecarPid>/clear_refs after prewarm (resets VmHWM), baseline VmRSS, then post-op VmHWM minus baseline (clamped >= 0). Idle-VM self-check runs once per matrix invocation and prints ~0 (measured 0B). - native/node lanes: live-child /proc VmHWM polling minus a measured nop startup baseline (native-baseline cpu_loop --iters 1 / node -e ''), floored to one page. GNU time -v is absent on this host, so /proc sampling is used uniformly. - Per-lane provenance strings recorded in results JSON; columns render '-' with a printed reason on non-Linux. Documented in the benchmarks README and CLAUDE.md §Benchmarks.
Member
Author
|
Stack for rivet-dev/secure-exec
Get stack: |
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
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.
Every latency-matrix op now reports peak memory attributable to the work, per
lane, plus memTax = guestPeak/nativePeak:
to /proc//clear_refs after prewarm (resets VmHWM), baseline
VmRSS, then post-op VmHWM minus baseline (clamped >= 0). Idle-VM self-check
runs once per matrix invocation and prints ~0 (measured 0B).
startup baseline (native-baseline cpu_loop --iters 1 / node -e ''), floored
to one page. GNU time -v is absent on this host, so /proc sampling is used
uniformly.
with a printed reason on non-Linux. Documented in the benchmarks README and
CLAUDE.md §Benchmarks.