test(benchmarks): concurrency and interference lanes#205
Merged
NathanFlurry merged 1 commit intoJul 2, 2026
Merged
Conversation
Three focused lanes measuring the multi-tenant behavior the single-op matrix
cannot see, wired as BENCH_ONLY lanes with JSON regression rows:
- concurrency-vms: N in {1,4,8} prewarmed VMs running a sustained echo loop.
Result: near-ideal isolation — 7.06x aggregate at N=8 (0.88 of ideal),
p95 5.5 -> 8.4ms.
- interference: busy VM (cpu+fs churn) beside a latency-probe VM. Result:
no measurable cross-VM tax on this host (p50 tax ~1.0).
- concurrent-processes: N in {1,4,8} guest processes in ONE VM. Result: the
per-VM single-threaded servicing ceiling — 2.18x at N=8 (0.27 of ideal),
p95 0.09 -> 0.21ms. This is the number the Phase 5 concurrency work moves.
Lanes self-assert N=1 agreement with the matrix ballpark and verify their
work; note: a persistent-listener TCP variant hits the sync-bridge deferred
message queue cap, so the TCP loop is connect/echo/close-shaped (cap noted
for follow-up).
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.
Three focused lanes measuring the multi-tenant behavior the single-op matrix
cannot see, wired as BENCH_ONLY lanes with JSON regression rows:
Result: near-ideal isolation — 7.06x aggregate at N=8 (0.88 of ideal),
p95 5.5 -> 8.4ms.
no measurable cross-VM tax on this host (p50 tax ~1.0).
per-VM single-threaded servicing ceiling — 2.18x at N=8 (0.27 of ideal),
p95 0.09 -> 0.21ms. This is the number the Phase 5 concurrency work moves.
Lanes self-assert N=1 agreement with the matrix ballpark and verify their
work; note: a persistent-listener TCP variant hits the sync-bridge deferred
message queue cap, so the TCP loop is connect/echo/close-shaped (cap noted
for follow-up).