Skip to content

feat(dispatch): implement Phase 16 strategy benchmarking #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
404khai merged 1 commit into from
Oct 6, 2026
Merged

feat(dispatch): implement Phase 16 strategy benchmarking #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions benchmarks/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,3 +108,13 @@ This is a correctness diagnostic, not a routing latency benchmark.
byte-identical replay; it does not compare dispatch strategies. See
[simulation documentation](../docs/simulation.md) and the
[measured artifact](results/2026-10-04-phase-15-simulation.json).

## Phase 16 dispatch strategy benchmarking

`roadrunner benchmark dispatch <scenario.json> [--idle-penalty-weight <weight>] [--json]`
replays identical inputs through four assignment policies and computes delivery durations,
waiting/idle time, distance, lateness, utilization, and explicit unfinished populations.
`scripts/collect_dispatch_strategy_benchmark.py` verifies paired/standalone replay and
records per-policy process timings with complete reproducibility metadata. See
[methodology](../docs/dispatch-strategy-benchmarks.md) and
[completion evidence](../docs/phase-16-completion.md).
Loading
Loading