Skip to content
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

Add basic benchmark harness #436

Merged
merged 1 commit into from
Oct 21, 2022
Merged

Add basic benchmark harness #436

merged 1 commit into from
Oct 21, 2022

Conversation

ToucheSir
Copy link
Member

A revamp of @dfdx's work in #304. The main changes here are running benchmarks and rendering the report on Buildkite instead of GHA, because the former gives us runners with >2 threads.

PR Checklist

  • Tests are added
  • Documentation, if applicable

@ToucheSir ToucheSir added the benchmark Run automated benchmarks on CI label Oct 13, 2022
@ToucheSir ToucheSir force-pushed the bc/benchmarks branch 6 times, most recently from 10bf133 to 89c5ebe Compare October 13, 2022 05:59
@ToucheSir
Copy link
Member Author

ToucheSir commented Oct 13, 2022

Unfortunately it's not possible to compare against master because no such benchmarking code exists there (that's why you'll see this step show up as failed on the latest commit). Therefore, I added an throwaway commit comparing HEAD vs HEAD to show an example of what the output would look like: https://buildkite.com/julialang/nnlib-dot-jl/builds/501#annotation-default.

Posting a GH comment would be far more difficult because of secret management and is best left for a future PR. If anyone finds an easier way to access the buildkite link, however, we could do something like what's currently in place for docs previews.

Co-authored by: Andrei Zhabinski <[email protected]>
Copy link
Member

@darsnack darsnack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, we can add more to the suite or solve the commenting issue separately.

Also, the documentation deployment issues should be resolved, and we can merge this to test that.

@ToucheSir ToucheSir closed this Oct 21, 2022
@ToucheSir ToucheSir reopened this Oct 21, 2022
@darsnack
Copy link
Member

Nice docs appear to be working

@ToucheSir ToucheSir merged commit fece619 into master Oct 21, 2022
@ToucheSir ToucheSir deleted the bc/benchmarks branch October 21, 2022 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Run automated benchmarks on CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants