Skip to content

Add controlled JDK cache benchmark scenario #10

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.

Sign up for GitHub

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

Merged
brunoborges merged 7 commits into from
Aug 5, 2026
Merged

Add controlled JDK cache benchmark scenario #10

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
fa14f16
Add JDK cache benchmark
brunoborges Aug 4, 2026
cd1fe9d
Enable branch benchmark dispatch
brunoborges Aug 4, 2026
fe91a0d
Restore focused benchmark dispatcher
brunoborges Aug 4, 2026
f11ace0
Apply batched suggestions from code review
brunoborges Aug 4, 2026
06b3b2b
Add JDK cache benchmark scenario
brunoborges Aug 5, 2026
35dffc6
Consolidate JDK cache benchmark PRs
brunoborges Aug 5, 2026
b269a66
Clarify consolidated benchmark comparison
brunoborges Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Clarify consolidated benchmark comparison 
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
  • Loading branch information
@brunoborges
brunoborges and Copilot committed Aug 5, 2026
commit b269a66ceb272e6b011cdd5794fef80a95f723cb
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ The **Focused cache restore** workflow isolates the setup step for comparing v4

### JDK cache

The **JDK cache** workflow measures the installed-JDK cache added on `actions/setup-java@main`. It compares a baseline arm with `cache-jdk: false` against a treatment arm with `cache-jdk: true`, defaulting to Microsoft Build of OpenJDK 17. Each arm first seeds its Maven dependency and wrapper caches by compiling Spring PetClinic. The treatment seed also downloads and saves the JDK. Warm matrix jobs then use `cache-read-only: true`, so they restore caches without creating entries or racing to save the same key.
The **JDK cache** workflow measures the installed-JDK cache added on `actions/setup-java@main`. It compares a baseline arm with `cache-jdk: false` against a treatment arm with `cache-jdk: true`, defaulting to Microsoft Build of OpenJDK 17. Both arms use the same action ref so the result isolates JDK caching instead of conflating it with implementation changes between commits. Each arm first seeds its Maven dependency and wrapper caches by compiling Spring PetClinic. The treatment seed also downloads and saves the JDK. Warm matrix jobs then use `cache-read-only: true`, so they restore caches without creating entries or racing to save the same key.

JDK cache keys are derived from the JDK's identity and source; unlike dependency cache keys, they cannot be namespaced per iteration. The seed/read-only design avoids cross-contamination between samples. Every seed and measurement job also removes matching JDKs from `$RUNNER_TOOL_CACHE` before setup, deliberately measuring the not-preinstalled path and preventing a hosted-runner tool-cache hit from bypassing JDK cache restore and save logic. Select Temurin to test that same forced-miss path with a distribution normally preinstalled on hosted runners.

Expand Down