Add flat vs. struct field projection benchmarks#21257
Merged
adriangb merged 1 commit intoapache:mainfrom Mar 30, 2026
Merged
Conversation
adriangb
approved these changes
Mar 30, 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.
Rationale for this change
This PR adds a benchmark comparing top-level column access against struct field access for the same logical data
#20925 introduced leaf level projection masking so that projecting a single struct field skips decoding its siblings. #21180 added benchmarks measuring that improvement across different strcut shapes. But neither benchmark answers how struct field access compare to reading the same column at the top level. Without that baseline, it's hard to know how much overhead the struct access path itself adds