Remove Performance section from README - #9
Merged
Conversation
Drop the hardcoded benchmark tables. They were measured on specific 2020/2019 machines with an old Go toolchain and no longer reflect current performance; keeping fixed numbers in the README invites staleness. The Benchmarking section still documents how to run them, and the new Benchmarks workflow can produce current numbers on demand.
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
1 participant
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.
Drop the hardcoded benchmark tables. They were measured on specific 2020/2019 machines with an old Go toolchain and no longer reflect current performance; keeping fixed numbers in the README invites staleness. The Benchmarking section still documents how to run them, and the new Benchmarks workflow can produce current numbers on demand.