Repository navigation
feat(dispatch): implement Phase 16 strategy benchmarking - #21
Merged
Merged
Conversation
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.
Phase 16 replays the same graph, orders, rider fleet, readiness seed, and traffic inputs through four independent dispatch policies: nearest feasible rider, lowest pickup ETA, readiness-aware lowest completion time, and preparation-aware assignment. The new
roadrunner benchmark dispatch <scenario.json> [--idle-penalty-weight <weight>] [--json]command reports observed delivery durations, pickup waiting and rider idle time, distance, lateness, utilization, and explicit unassigned/unfinished populations.All strategies share eligibility, road feasibility, deterministic RiderId tie breaking, decision evidence, and atomic assignment. Completion-time ranking includes readiness with zero waiting penalty; existing
basicretains its road-travel objective. Nearest ranking records its meter-valued distance separately from informational travel seconds.The collector verifies exact paired replay and standalone equivalence, then records hardware, dataset/graph identities, configuration, compiler/binary hash, raw process timings and median/p95/p99. Two committed synthetic comparisons use eleven measured runs per policy. They demonstrate different proximity/ETA and preparation-penalty behavior without claiming universal strategy superiority or production scalability. Methodology and completion evidence are in
docs/dispatch-strategy-benchmarks.mdanddocs/phase-16-completion.md.Validation:
cargo +1.99.0 test --workspace --all-features --locked: 138 tests pass; doc tests pass.git diff --checkpass.