-
Notifications
You must be signed in to change notification settings - Fork 323
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
Ensure that bench downloading script downloads artifacts from correct job #9355
Comments
It'd be even better if the official benchmark results displayed values from both GraalVM versions. Each in different color. At the end the goal is to find out why using Oracle GraalVM is better than sticking with GraalVM CE. Performance is likely one of the reasons. Having such reason directly that visible in the benchmarks result might be the convincing point. |
First successful The uploaded Runtime Benchmark Report artifact contains results from the Engine Benchmarks (GraalVM CE). There are no artifacts for the
|
Preliminary manual comparison of
|
Re. Otherwise the improvements look very nice! |
Related to the work done in #5709 |
Pavel Marek reports a new STANDUP for today (2024-06-10): Progress: - Making sure that results from Oracle GraalVM benchmarks are persistent.
|
Pavel Marek reports a new STANDUP for today (2024-06-11): Progress: - Closing stale PRs
|
Add #9355 (comment) : No artifacts for Oracle GraalVM benchmark job means that we have to gather the data from the job output. Note that job outputs also expire after 3 months, like artifacts. |
Last 3 months of Oracle GraalVM bench results persisted in 70cb785 |
Pavel Marek reports a new STANDUP for today (2024-06-12): Progress: - Results from Oracle GraalVM benchmark runs gathered in #10224 (comment)
|
A follow-up of #9322. The Benchmark Engine workflow now has two jobs. One that runs with
Oracle GraalVM
and another one that runs withGraalVM CE
. Ensure that the website_regen.py fetches artifacts from theGraalVM CE
job so far.The text was updated successfully, but these errors were encountered: