Repository navigation
Conversation
This comment has been minimized.
This comment has been minimized.
Contributor
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
This branch has not been deployed
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 does this PR do?
Tunes the upstream system-test desired_execution_time using measured CI Visibility durations to minimize end-to-end workflow wall time. This is isolated from the separate Gradle clean experiment in #12785.
Selected target: 12.5 minutes (248 shards). It stays below the upstream 256-job cap while reducing the slow tail substantially.
Results
The two 12.5-minute runs average 31m03s, 6m41s or 17.7% faster than the 15-minute control. Both also reduced the slowest shard by more than four minutes.
The 20-minute treatment used fewer runner-minutes but slowed the pipeline. The 12-minute treatment hit the 256-shard cap and regressed wall time. The 13-minute treatment reduced startup count but regressed wall time, p95, maximum, and runner cost. Together these bound the fastest observed target at 12.5 minutes.
The planner consumes historical duration data from system-tests time-stats.json and uses first-fit-decreasing allocation; it does not currently query live CI Visibility data. CI Visibility is used here to measure and select the target.
Inspired by DataDog/dd-trace-rb#6439, while keeping setup-cost changes outside this PR.
Validation