hide: LAN-52 add benchmark display executable#17
Merged
Conversation
added 2 commits
March 24, 2026 16:32
winitzki
changed the title
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
3 participants
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 PR adds a CLI tool that renders benchmark graphs to a standalone HTML file (using the same Plotly graph style as the web UI) and opens it locally.
The data is taken from JSON files that the benchmark outputs.
In this way, local development can be faster - each benchmark graph can be visualized on the local machine in the same way it will appear in CI, without waiting for CI.
This will work if the benchmark writes its data as JSON. Currently the full benchmark run does this (
bench.sh) as well as individual benchmarks: bench-csv-table.sh and bench-complex-spec.sh.The tool can take several JSON files (several benchmark runs) and plot the results as lines. If JSON files have git hashes in their names then the git hashes will be used for the graph legends.
Alternatively, data can be taken from the local sqlite3 database (downloaded from brossa.io).