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

Airspeed Velocity #42

Open
alecandido opened this issue Feb 16, 2023 · 4 comments
Open

Airspeed Velocity #42

alecandido opened this issue Feb 16, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@alecandido
Copy link
Member

alecandido commented Feb 16, 2023

This is the typical setup that works well inside asv.

We can rearrange benchmarks in asv layout, run them in the CI, and publish the report on GitHub pages. Similar to what NumPy is doing:
https://pv.github.io/numpy-bench/

@liweintu
Copy link
Contributor

Ok. Maybe we can take care of the rearrangement for asv first, then address issue #41.

@alecandido
Copy link
Member Author

Ok. Maybe we can take care of the rearrangement for asv first, then address issue #41.

It is just a proposal and an improvement, I would not consider blocking for @liweintu #41. But if you want to keep going with this one first, that is perfectly feasible (and I'd also personally like to see the report :D)

@alecandido alecandido added the enhancement New feature or request label Feb 16, 2023
@liweintu
Copy link
Contributor

Ok. Maybe we can take care of the rearrangement for asv first, then address issue #41.

It is just a proposal and an improvement, I would not consider blocking for @liweintu #41. But if you want to keep going with this one first, that is perfectly feasible (and I'd also personally like to see the report :D)

I see. How about we address issue #41 first to add our first TNet backend quimb into the benchmarking, then take care of this issue for asv in a new PR.

@alecandido
Copy link
Member Author

I see. How about we address issue #41 first to add our first TNet backend quimb into the benchmarking, then take care of this issue for asv in a new PR.

Perfectly fine as well :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: 🆕 New
Development

No branches or pull requests

2 participants