test(benchmarks): two-tier sizes for payload-sensitive ops#204
Merged
NathanFlurry merged 1 commit intoJul 2, 2026
Conversation
Normalizes the size-variant zoo into exactly two tiers per payload-sensitive op, named <op>_small/<op>_big (fs read/write 4KiB/1MiB, socket echo 16B/64KiB, readdir 32/1000 entries, stream copy 64KiB/1MiB, spawn capture, pass-through), 63 -> 70 matrix ops. Count/shape ops (tcp_tiny_writes_16, backpressure_chunks) keep their names with clarifying comments. Renames are tabled in the README (small_write->fs_write_small, big_read->fs_read_big, readdir_large-> readdir_small, stream_copy_1m->stream_copy_big, tcp_echo->tcp_echo_small, tcp_throughput_64k->tcp_echo_big, throughput_64k->pass_through_big, spawn_stdout_256k_capture->spawn_stdout_capture_big); native-baseline gained the size knobs the new tiers needed, with three explicitly-commented borrowed stand-ins left for Phase 2 (native stream-copy, unix echo). Baseline continuity intentionally breaks here; 1.7 regenerates on the canonical environment.
Member
Author
|
Stack for rivet-dev/secure-exec
Get stack: |
railway-app
Bot
temporarily deployed
to
secure-exec / secure-exec-pr-204
NathanFlurry
deleted the
stack/test-benchmarks-two-tier-sizes-for-payload-sensitive-ops-worxzxsu
branch
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5343
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5328
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5314
railway-app
Bot
requested a deployment
to
rivet-frontend / agentos-pr-1507
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5333
railway-app
Bot
requested a deployment
to
rivet-frontend / agentos-pr-1510
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5324
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5338
railway-app
Bot
requested a deployment
to
rivet-frontend / rivet-pr-5320
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.
Normalizes the size-variant zoo into exactly two tiers per payload-sensitive
op, named _small/_big (fs read/write 4KiB/1MiB, socket echo 16B/64KiB,
readdir 32/1000 entries, stream copy 64KiB/1MiB, spawn capture, pass-through),
63 -> 70 matrix ops. Count/shape ops (tcp_tiny_writes_16, backpressure_chunks)
keep their names with clarifying comments. Renames are tabled in the README
(small_write->fs_write_small, big_read->fs_read_big, readdir_large->
readdir_small, stream_copy_1m->stream_copy_big, tcp_echo->tcp_echo_small,
tcp_throughput_64k->tcp_echo_big, throughput_64k->pass_through_big,
spawn_stdout_256k_capture->spawn_stdout_capture_big); native-baseline gained
the size knobs the new tiers needed, with three explicitly-commented borrowed
stand-ins left for Phase 2 (native stream-copy, unix echo). Baseline
continuity intentionally breaks here; 1.7 regenerates on the canonical
environment.