feat(parquet): add sparse-column writer benchmarks#9654
Merged
Conversation
Add three new benchmark cases to the arrow_writer benchmark suite for evaluating write performance on sparse and all-null data: - `primitive_sparse_99pct_null`: a flat primitive column with 99% nulls, exercising long RLE runs in definition levels. - `list_primitive_sparse_99pct_null`: a list-of-primitive column with 99% nulls, exercising null batching in the list level builder. - `primitive_all_null`: a flat primitive column with 100% nulls, exercising the uniform_levels fast path for entirely-null columns. Baseline results (Apple M1 Max): primitive_sparse_99pct_null/default 40.3 ms primitive_sparse_99pct_null/parquet_2 43.5 ms primitive_sparse_99pct_null/zstd_parquet_2 44.4 ms list_primitive_sparse_99pct_null/default 39.9 ms list_primitive_sparse_99pct_null/parquet_2 39.9 ms list_primitive_sparse_99pct_null/zstd_p2 40.7 ms primitive_all_null/default 38.0 ms primitive_all_null/parquet_2 36.9 ms primitive_all_null/zstd_parquet_2 36.1 ms Signed-off-by: Hippolyte Barraud <hippolyte.barraud@datadoghq.com>
Contributor
|
I'm holding off merging in case we want to add more cases. |
Contributor
|
Are we still waiting on edge cases? |
Contributor
Yes, but I don't think we need to hold this up for them. They can be a separate PR if necessary. |
Contributor
|
🚀 |
Rich-T-kid
pushed a commit
to Rich-T-kid/arrow-rs
that referenced
this pull request
Jun 2, 2026
# Which issue does this PR close? - None, but relates to apache#9652 # Rationale for this change Measure sparse and all-null cases in benchmarks. # What changes are included in this PR? Add three new benchmark cases to the arrow_writer benchmark suite for evaluating write performance on sparse and all-null data: - `primitive_sparse_99pct_null`: a flat primitive column with 99% nulls, exercising long RLE runs in definition levels. - `list_primitive_sparse_99pct_null`: a list-of-primitive column with 99% nulls, exercising null batching in the list level builder. - `primitive_all_null`: a flat primitive column with 100% nulls, exercising the uniform_levels fast path for entirely-null columns. # Are these changes tested? N/A # Are there any user-facing changes? None. Signed-off-by: Hippolyte Barraud <hippolyte.barraud@datadoghq.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
3 participants
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
Measure sparse and all-null cases in benchmarks.
What changes are included in this PR?
Add three new benchmark cases to the arrow_writer benchmark suite for evaluating write performance on sparse and all-null data:
primitive_sparse_99pct_null: a flat primitive column with 99% nulls, exercising long RLE runs in definition levels.list_primitive_sparse_99pct_null: a list-of-primitive column with 99% nulls, exercising null batching in the list level builder.primitive_all_null: a flat primitive column with 100% nulls, exercising the uniform_levels fast path for entirely-null columns.Are these changes tested?
N/A
Are there any user-facing changes?
None.