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

Display most recent benchmarks #53

Closed
jordandsullivan opened this issue Oct 11, 2024 · 0 comments · Fixed by #151
Closed

Display most recent benchmarks #53

jordandsullivan opened this issue Oct 11, 2024 · 0 comments · Fixed by #151
Assignees
Labels
infrastructure Non-quantum things to improve the robustness of our package, e.g. CI/CD
Milestone

Comments

@jordandsullivan
Copy link
Collaborator

Currently our benchmarks are visible in a ucc/benchmarks Jupyter notebook, but this is only as accurate as the last time it was run and all the specifics of the individual developer's OS and the versions they used.

The idea with this issue is to systematize the benchmarking to run, say, every time someone merges with main and prominently display the benchmarking results in our README via (most likely) a Github Action.

@jordandsullivan jordandsullivan added the infrastructure Non-quantum things to improve the robustness of our package, e.g. CI/CD label Oct 16, 2024
@jordandsullivan jordandsullivan added this to the 0.3.0 milestone Dec 1, 2024
@jordandsullivan jordandsullivan self-assigned this Dec 6, 2024
@jordandsullivan jordandsullivan linked a pull request Dec 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Non-quantum things to improve the robustness of our package, e.g. CI/CD
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant