Skip to content

Add performance results dashboard subproject#4277

Merged
andimarek merged 3 commits intomasterfrom
performance-results-page
Mar 2, 2026
Merged

Add performance results dashboard subproject#4277
andimarek merged 3 commits intomasterfrom
performance-results-page

Conversation

@andimarek
Copy link
Member

@andimarek andimarek commented Mar 2, 2026 •
edited
Loading

Summary

  • Adds performance-results-page subproject that parses JMH JSON result files from performance-results/ and generates an interactive HTML dashboard with Chart.js charts
  • Updates the GitHub Pages workflow (static.yml) to run the Gradle task with JDK 21 and deploy the generated output instead of a static pages/ directory
  • Covers all 242 result files across 11 benchmark classes with throughput/avg-time charts, navigation TOC, and latest-results tables

Test plan

  • ./gradlew :performance-results-page:generatePerformancePage completes successfully
  • Generated index.html renders correctly in a browser with interactive charts
  • Verify GitHub Pages deployment works after merge

🤖 Generated with Claude Code

andimarek and others added 2 commits March 2, 2026 18:06
@andimarek @claude
Add performance-results-page subproject to generate benchmark dashboard
1be6ac5 
Adds a Java tool that parses JMH JSON result files from performance-results/
and generates an interactive HTML dashboard with Chart.js charts, deployed
via the existing GitHub Pages workflow.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@andimarek @claude
Generate index.html inside subproject build dir and update Pages work…
54597be 
…flow

Output now goes to performance-results-page/build/site/ instead of pages/.
The GitHub Actions workflow runs the Gradle task with JDK 21 before deploying.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2026 •
edited
Loading

Test Results

  335 files  ±0    335 suites  ±0   5m 6s ⏱️ -3s
5 380 tests ±0  5 372 ✅ ±0  8 💤 ±0  0 ❌ ±0 
5 469 runs  ±0  5 461 ✅ ±0  8 💤 ±0  0 ❌ ±0 

Results for commit 5cb39d7. ± Comparison against base commit a0449b5.

This pull request removes 175 and adds 151 tests. Note that renamed tests count towards both. 
	?

	, expected: combo-\"\\\b\f\n\r\t, #4]
                __schema { types { fields { args { type { name fields { name }}}}}}
                __schema { types { fields { type { name fields { name }}}}}
                __schema { types { inputFields { type { inputFields { name }}}}}
                __schema { types { interfaces { fields { type { interfaces { name } } } } } }
                __schema { types { name} }
                __type(name : "t") { name }
                a1: __schema { types { name} }
                a1: __type(name : "t") { name }
…

graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure23@717d7587 delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure24@2489e84a delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args but false does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_21prov0_closure25@2fd954f delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure20@7c51782d delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure21@4fe533ff delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertFalse with different number of error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_20prov0_closure22@5d5b9ecb delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure3@6468a7b6 delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1, #0]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure4@2121d1f9 delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2, #1]
graphql.AssertTest ‑ assertNotNull with different number of  error args throws assertions [toRun: <graphql.AssertTest$__spock_feature_0_5prov0_closure5@46e64760 delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1 arg2 arg3, #2]
graphql.AssertTest ‑ assertNotNull with different number of error args with non null does not throw assertions [toRun: <graphql.AssertTest$__spock_feature_0_6prov0_closure6@60c73e58 delegate=inaccessible owner=inaccessible thisObject=inaccessible resolveStrategy=inaccessible directive=inaccessible parameterTypes=inaccessible maximumNumberOfParameters=inaccessible bcw=inaccessible thisType=inaccessible>, expectedMessage: error arg1, #0]
…

♻️ This comment has been updated with latest results.

@andimarek @claude
Enhance dashboard with date range filter, class selector, and per-ser…
5cb39d7 
…ies charts

- Add date range filter bar with preset buttons (30d, 90d, 6mo, all time)
- Turn nav into a class filter that shows/hides sections
- Give each benchmark series (method+mode+params) its own chart
- Tables update dynamically with the date filter

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@andimarek andimarek merged commit 32c996c into master Mar 2, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@andimarek