Skip to content

[SPARK-60848][TESTS] Regenerate benchmark results after bumping the minimum Java to 21 - #60064

Draft
dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-60848
Draft

dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-60848

Conversation

@dongjoon-hyun

@dongjoon-hyun dongjoon-hyun commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

This PR aims to regenerate the benchmark results after bumping the minimum Java version to 21 (SPARK-60669).

Why are the changes needed?

After SPARK-60669, Java 21 is the minimum Java version of Apache Spark 5.0.0, and BenchmarkBase uses Java 21 as its base (SPARK-60831). The default benchmark results were generated with the previous baseline (Java 17), so they no longer represent the supported minimum Java version. Regenerating them keeps the results consistent with the current baseline and the JDK 25 results.

Currently, Apache Spark benchmark CI has been broken like the following. This PR will detect those issues.

Does this PR introduce any user-facing change?

No. This PR only updates the benchmark result files.

How was this patch tested?

Manually reviewed. The result files were generated by running the benchmarks in GitHub Actions (JDK 21 and JDK 25, Scala 2.13, split 1-64) according to https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude Sonnet 5.5

@dongjoon-hyun

dongjoon-hyun commented Nov 3, 2026 •

Copy link
Copy Markdown
Member Author

Currently, thesis a draft because the benchmarks are running here in order to make it sure that all data are in sync in terms of the generation time and the expected CPU model (AMD EPYC 7763). Lastly, this will make it sure that there is no the missing files.

Please note that I need to re-trigger the subset of test pipelines multiple times because the benchmark run will fail at the startup if the expected CPU model is not AMD EPYC 7763 .

@HyukjinKwon HyukjinKwon added the ai-review-requested Trigger AI review by Omnigent on Databricks label Nov 3, 2026
@spark-test

Copy link
Copy Markdown
Collaborator

The AI review requested by @HyukjinKwon did not finish. A committer can add the ai-review-requested label again to retry.

@dongjoon-hyun

Copy link
Copy Markdown
Member Author

Rebase to master to sync with master in order to generate the latest result.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants