Add benchmark for decoding LEB128 encoded u64 values #501
Conversation
This file contains 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
This change adds a benchmark for the decoding of LEB128 encoded u64 values. We decode a bunch of values in a single benchmark iteration, to magnify the number granularity a bit (should we ever decide to optimize a duration of 2ns per iteration doesn't give much leeway). > test util::tests::bench_u64_leb128_reading ... bench: 118 ns/iter (+/- 13) Signed-off-by: Daniel Müller <deso@posteo.net>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #501 +/- ##
==========================================
+ Coverage 93.51% 93.53% +0.02%
==========================================
Files 45 45
Lines 7951 7980 +29
==========================================
+ Hits 7435 7464 +29
Misses 516 516 ☔ View full report in Codecov by Sentry. |
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.
This change adds a benchmark for the decoding of LEB128 encoded u64 values. We decode a bunch of values in a single benchmark iteration, to magnify the number granularity a bit (should we ever decide to optimize a duration of 2ns per iteration doesn't give much leeway).