bench(parquet): add nested list writer benchmarks#10084
Open
mapleFU wants to merge 1 commit into
Open
Conversation
Add benchmarks for list types with nested repetition levels: - `list_nested`: List<List<Int32>> - `list_struct_with_list`: List<Struct<a:Int32, b:Float32, c:List<Int32>>> These exercise the per-slot (non-batched) write path where child_has_no_nested_rep() returns false, providing a baseline for future optimizations. Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
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.
Which issue does this PR close?
Rationale for this change
Add benchmarks for list types with nested repetition levels:
list_nested: List<List>list_struct_with_list: List<Struct<a:Int32, b:Float32, c:List>>These exercise the per-slot (non-batched) write path where child_has_no_nested_rep() returns false, providing a baseline for future optimizations.
What changes are included in this PR?
Add some benchmarks
Are these changes tested?
They're already tests
Are there any user-facing changes?
No