-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
What is the max time a benchmark should take? #8
Comments
Good question, we need not test all commits to find big regressions: so that would mean that it's not too bad having long running benchmarks. Ideally I think benchmarks should be on the order of a few seconds, but maybe a few benchmarks being on the order of minute(s) is alright if motivated? (e.g. perfomance regressions wouldn't show up in smaller benchmarks) |
I thinking shorter benchmarks that test the core will be very important. But we may need some longer ones of solve, simplification, etc. And like you say, if a longer one is introduced we should be sure it is required to demonstrate the regressions. |
An other option is to have a separate benchmark folder for very long running benchmarks and have a special asv.conf.json file pointing to this folder (or add some magic to ./run_benchmarks.sh). |
Here are the latest timings on my benchmark machine:
The are a few above 4 seconds, which is long. It'd be nice to keep all benchmarks under a second at least. |
@bjodah What do you think is a reasonable max time for a single benchmark?
The text was updated successfully, but these errors were encountered: