Conversation
Link the new project website (benchkit.dev) and add a canonical quick start: pip install plus the runnable version of Listing 1 of the ICPE 2026 paper, using the current campaign API (top-level CampaignCartesianProduct, LevelDBBench with bench_name as a variable). The README previously showed no campaign example at all, while the paper, the website, and the reproduction artifact all showcase this one. Rewrite the supported-benchmarks section to match reality: SPEC CPU 2017 and SPEC CPU 2026 first, the full benchkit.benches roster (NPB, Graph500, Splash-4, VolanoMark, ...), and the examples/ integrations listed separately; drop the stale TODO markers. Point Getting Started at the ICPE reproduction artifact (9 verified examples on the current API) and mark the tutorials and examples/ integrations as legacy campaign API, with a matching notice in both tutorial READMEs. Signed-off-by: Antonio Paolillo <apaolill@gmail.com>
EstAK
approved these changes
Jul 22, 2026
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
2 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.
Link the new project website (benchkit.dev) and add a canonical quick start: pip install plus the runnable version of Listing 1 of the ICPE 2026 paper, using the current campaign API (top-level CampaignCartesianProduct, LevelDBBench with bench_name as a variable). The README previously showed no campaign example at all, while the paper, the website, and the reproduction artifact all showcase this one.
Rewrite the supported-benchmarks section to match reality: SPEC CPU 2017 and SPEC CPU 2026 first, the full benchkit.benches roster (NPB, Graph500, Splash-4, VolanoMark, ...), and the examples/ integrations listed separately; drop the stale TODO markers.
Point Getting Started at the ICPE reproduction artifact (9 verified examples on the current API) and mark the tutorials and examples/ integrations as legacy campaign API, with a matching notice in both tutorial READMEs.