feat(parquet): add struct-column writer benchmarks#9679
Merged
alamb merged 1 commit intoapache:mainfrom Apr 9, 2026
Merged
Conversation
Add three new benchmark cases to the arrow_writer benchmark suite for evaluating write performance on struct columns at varying null densities: - `struct_non_null`: a nullable struct with 0% null rows and non-nullable primitive children; - `struct_sparse_99pct_null`: a nullable struct with 99% null rows, exercising null batching through one level of struct nesting; - `struct_all_null`: a nullable struct with 100% null rows, exercising the uniform-null path through struct nesting. Baseline results (Apple M1 Max): struct_non_null/default 29.9 ms struct_non_null/parquet_2 38.2 ms struct_non_null/zstd_parquet_2 50.9 ms struct_sparse_99pct_null/default 7.2 ms struct_sparse_99pct_null/parquet_2 7.3 ms struct_sparse_99pct_null/zstd_p2 8.1 ms struct_all_null/default 83.3 µs struct_all_null/parquet_2 82.5 µs struct_all_null/zstd_parquet_2 106.6 µs Signed-off-by: Hippolyte Barraud <hippolyte.barraud@datadoghq.com>
1d00df3 to
85c10b4
Compare
alamb
approved these changes
Apr 9, 2026
Contributor
|
Thank you @HippoBaro |
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.
Which issue does this PR close?
Rationale for this change
#9653 introduces optimizations related to non-null uniform workloads. This adds benchmarks so we can quantify them.
What changes are included in this PR?
Add three new benchmark cases to the arrow_writer benchmark suite for evaluating write performance on struct columns at varying null densities:
struct_non_null: a nullable struct with 0% null rows and non-nullable primitive children;struct_sparse_99pct_null: a nullable struct with 99% null rows, exercising null batching through one level of struct nesting;struct_all_null: a nullable struct with 100% null rows, exercising the uniform-null path through struct nesting.Baseline results (Apple M1 Max):
Are these changes tested?
N/A
Are there any user-facing changes?
None