Repository navigation
[P8-00] Consolidate performance recovery evidence and remaining gates - #596
Merged
Merged
Conversation
14 tasks
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 8 results were spread across child reports, while the local roadmap/backlog omitted the phase and the public benchmark ledger still called merged Sparse Blossom work unmerged. Add an integration report with actual timing/output/memory boundaries, raw-data links, default versus opt-in adoption, negative results and explicit remaining gates. Restore the 17 existing issue specifications to BACKLOG.md and link the report from ROADMAP.md and benchmarking guidance.
Refs #550. This is an interim integration report: 13/16 capabilities are closed; #551, #561 and #562 remain open. The tracker must stay open. Draft #569 is unchanged; no unmeasured Metal/multi-GPU verdict is claimed. Existing measurements retain their historical source identities and are not multiplied into a phase-wide speedup.
Validation: fresh release CPU CLI build; 32 Rust and 16 Python tests passed, including the real public CLI receipt guard; one existing external PyMatching test remains ignored. All six saved server campaigns revalidate, preserving four executed, one failed and one contaminated classifications. Bell CLI smoke, local Markdown link/17-specification/state-count checks, rustfmt and diff checks passed. Headline lazy-transfer/sampling/public-fusion values were recomputed from retained JSON. Exact commands, CLI hash and logs are under docs/perf/data/p8-00/.
No production code changed. No new performance, GPU, Metal or remote-server campaign was run. Manual self-review found no blocking documentation findings; this is not an independent review.