[SPARK-56120][PYTHON][TEST] Add ASV micro-benchmarks for SQL_WINDOW_AGG_ARROW_UDF#55056
Closed
Yicong-Huang wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-56120][PYTHON][TEST] Add ASV micro-benchmarks for SQL_WINDOW_AGG_ARROW_UDF#55056Yicong-Huang wants to merge 1 commit intoapache:masterfrom
Yicong-Huang wants to merge 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
wait for fix in #55059 |
09348d5 to
4513cfa
Compare
zhengruifeng
approved these changes
Mar 31, 2026
Contributor
|
merged to master |
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.
What changes were proposed in this pull request?
Add ASV micro-benchmarks for
SQL_WINDOW_AGG_ARROW_UDF.Also adds optional
runner_confparameter toMockProtocolWriter.write_worker_inputfor passing configuration likewindow_bound_types.Why are the changes needed?
Part of SPARK-55724. Establishes performance baselines before refactoring this eval type.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No.