-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-34387][CORE][TESTS] Add ZStandardBenchmark #31498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test build #134960 has finished for PR 31498 at commit
|
|
Could you review this PR, @HyukjinKwon , @maropu , @viirya ? This is a baseline for ZStandardCompression to prevent any regression in the future. |
maropu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine
|
Merged to master because this is irrelevant to the UT or IT. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
HyukjinKwon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm2
|
Thank you, @HyukjinKwon ! |
|
Test build #134964 has finished for PR 31498 at commit
|
### What changes were proposed in this pull request? This PR aims to add ZStandardBenchmark as a base-line. ### Why are the changes needed? This will prevent any regression when we upgrade Zstandard library in the future. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manually. Closes apache#31498 from dongjoon-hyun/SPARK-ZSTD-BENCH. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
This PR aims to add ZStandardBenchmark as a base-line.
Why are the changes needed?
This will prevent any regression when we upgrade Zstandard library in the future.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually.