-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
benchmarks for ode #69
Comments
As a starting point we should benchmark dsolve itself rather than the individual hints. Then we can see if changing the hints used leads to speed up or slowdown. For the examples to pick I would aim for relatively common cases and examples that can be particularly fast or slow rather than trying to cover everything like the tests do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the dsolve benchmarks, only one benchmark is present for now. I am trying to add dsolve benchmarks but I am a little bit confused that how should I start?
So can someone help me?
sympy_benchmarks/benchmarks/dsolve.py
Line 19 in 7d0835a
For the dsolve, I am thinking to add benchmarks for all the hints one by one like for
factorable
-So should I proceed like this?
If yes, then I have a few questions-
If I add a benchmark for, let's say
factorable
method, so for that (like above), I will have to add at least one(maybe only one) equation to test. If I will add only one equation, then how we can say about slowing or speeding of a method based on only one equation.And If we will add more than one equations to test, then maybe it can be too slow to benchmark the method.
If No, then how should I proceed?
CC @oscarbenjamin
The text was updated successfully, but these errors were encountered: