This repository has been archived by the owner on Mar 1, 2022. It is now read-only.
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.
Add cabal bench package with a dummy benchmark, as base for #9
@TotallyNotChase Feel free to add your benchmarks here. If you are not using
criterion
feel free to remove it, but it would be nice to be able to generate the benchmark report in JSON (criterion does this automatically for us), so that we can integrate it to CI for a nicer report like IntersectMBO/plutus#3494 (comment) ... edit: actually, it may be a good idea to usecriterion
here because we get cheap comparison tools (see next paragraph).@MatthewCroughan
nix build '.#pluton:bench:perf'
followed by running./result/bin/perf
generates abench.json
as well asbench.csv
that can be used to generate the CI report (there is alsobench.html
for the corresponding HTML view). There is even criterion-compare which seems to do the heavy-lifting here. cf. haskell/criterion#151