docs: simplify performance guidance and centralize benchmark snapshots#190
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.
Motivation
Description
docs/concepts/performance-comparisons.mdwith a concise decision guide that includes a TL;DR tool-selection matrix, honest performance positioning, and a fast-path tuning checklist.docs/concepts/benchmark-results.mdinto a raw-snapshot hub with a canonical snapshot template and instructions to treatbenchmarks/comparison_results/as the source of truth.Testing
cargo fmt --all, which completed successfully.cargo clippy --all-targets --all-features -- -D warnings, which completed successfully with no warnings.cargo test, which completed successfully (1047tests passed).just fmtbut thejusttool is not installed in this environment, so that external check could not be executed here.Codex Task