Normalize historic benchmark data after adding OperationsPerInvocation annotation#8100
Merged
jack-berg merged 1 commit intoopen-telemetry:benchmarksfrom Feb 18, 2026
Merged
Conversation
trask
approved these changes
Feb 18, 2026
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.
In #8031 we updated the benchmarks to output actual operation figures instead of aggregate operations (where each operation performs a loop of 1024*10 operations).
See comment1 and comment2.
This screws up the benchmark history because all the figures now look 1024*10x higher than previously.
This PR fixes the issue by multiplying all benchmark figures prior to #8031 by 1024*10.
Current benchmark:
Benchmark with this PR:
Expand to see untracked one-off script used to make the change