Drive JMH benchmarks via Apache Zeppelin. #335
Draft
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.
This is some early work that allows using Apache Zeppelin to drive, organize, visualize, and explore our jmh benchmarks.
It's not quite ready to be used more broadly, there are a few things that would not be addressed outside it's normal location.
Some of it is messy and early and exploratory. How or if or where it could one day be more widely shared is a mystery.
But as a start, it will be right here, on this branch, in this PR. It's not a home, but it will do as a tmp couch.
Via this tool you can generate various benchmark reports that can visualize before and after results, track and graph system stats, ssh benchmarks to other hardware, display flamegraphs, analyze gc and heapdumps, etc. A report might end up resembling something like (the data in this one is stale, incomplete, in some in between states and non valuable atm, but serves as an example report):