Add reasoning-pattern benchmark scaffold#435
Draft
LIU-ZHIYUAN-source wants to merge 3 commits into
Draft
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.
Summary
This PR adds an initial benchmark scaffold for comparing inferlet-based reasoning patterns in Pie.
It includes:
pie runwith local wasm + manifest + configValidation
Tested locally / on RunPod with:
cargo fmt --manifest-path inferlets/reasoning-benchmark/Cargo.tomlcargo test --manifest-path inferlets/reasoning-benchmark/Cargo.tomlpython3 -m unittest benches.test_reasoning_bench./target/release/pie runSmall sanity experiments:
<think>after the benchmark-local cue workaroundNotes
This PR focuses on benchmark infrastructure, not final benchmark results. The current GSM8K-10 runs are only sanity checks and are not statistically meaningful.
Follow-up
This initial scaffold keeps all reasoning patterns in one benchmark inferlet for rapid validation. A planned follow-up is to split the patterns into separate inferlets and introduce a base text-completion inferlet, so user-submitted test-time scaling inferlets can be run and scored in isolation.