-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically run go benchmarks #338
Milestone
Comments
mhutchinson
added a commit
to mhutchinson/trillian-tessera
that referenced
this issue
Dec 9, 2024
Merged
mhutchinson
added a commit
to mhutchinson/trillian-tessera
that referenced
this issue
Dec 9, 2024
mhutchinson
added a commit
that referenced
this issue
Dec 9, 2024
This is intended for the benchmark data in #338.
Cool, looks like we have some benchmark data now: https://transparency-dev.github.io/trillian-tessera/dev/bench/ This meant setting up a permanent branch in this repo at |
mhutchinson
added a commit
to mhutchinson/trillian-tessera
that referenced
this issue
Dec 16, 2024
Make sure there's always an easy to find link. transparency-dev#338.
mhutchinson
added a commit
that referenced
this issue
Dec 16, 2024
Make sure there's always an easy to find link. #338.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a few benchmarks for critical code in this repo. These benchmarks aren't run in CI. An ideal workflow would allow PRs to be flagged if they cause regressions in these benchmarks. We would also be able to see how the benchmarks have changed over time.
https://github.com/benchmark-action/github-action-benchmark promises to do this.
The text was updated successfully, but these errors were encountered: