[SPARK-58415][TESTS] Regenerate benchmark results - #57620
Closed
dongjoon-hyun wants to merge 189 commits into
Closed
[SPARK-58415][TESTS] Regenerate benchmark results#57620dongjoon-hyun wants to merge 189 commits into
dongjoon-hyun wants to merge 189 commits into
Conversation
Member
Author
|
Could you review this PR, @LuciferYang ? While I'm checking it, I realized that it's quite outdated. I regenerated the result. |
dongjoon-hyun
marked this pull request as draft
July 29, 2026 05:05
LuciferYang
approved these changes
Jul 29, 2026
Member
Author
|
Thank you, @LuciferYang ! |
dongjoon-hyun
marked this pull request as ready for review
July 29, 2026 07:50
Member
Author
|
Merge Summary:
Posted by |
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
2 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.
What changes were proposed in this pull request?
This PR aims to regenerate benchmark results to check the intermediate status as a part of Apache Spark 5.0.0 preparation
Why are the changes needed?
To make the benchmark up-to-date and fill the missing gaps in order to help the comparison with the upcoming Apache Spark 4.3.0.
1. Last Update (2026-02-13)
2. Java Version Changes
3. MISSING BENCHMARK RESULT
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.