bench: add Skiff format throughput coverage - #51
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.
Summary
Dynamic decoding result
The direct decode comparison uses 100,000 identical rows per iteration and reads the duration field from each decoded dynamic value. It reports rows per second, rather than bytes per second, because the two wire formats have different encoded sizes.
On the Apple M1 Max / rustc 1.94.0 setup, Skiff was 3.19x faster for this dynamic-job-API comparison.
Dynamic encoding result
The paired encode comparison constructs the same 100,000 logical rows as a keyed YsonValue map or positional Skiff Value tuple, then emits one complete table stream. It includes dynamic row construction and the format record separator or table tag.
Skiff was 2.71x faster for this dynamic encode path.
These are results for the current Rust dynamic APIs and their differing row representations. They are not protocol-wide claims or predictions for typed, borrowed YSON jobs.
Validation