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

A better way to benchmark the speed tests #782

Closed
Ban-zee opened this issue Aug 1, 2019 · 2 comments · Fixed by #1142
Closed

A better way to benchmark the speed tests #782

Ban-zee opened this issue Aug 1, 2019 · 2 comments · Fixed by #1142
Labels
Enhancement Improvements to ArviZ Help Wanted

Comments

@Ban-zee
Copy link
Contributor

Ban-zee commented Aug 1, 2019

The benchmark tests which are in use now can be improved much more. Importing arviz into the benchmark tests throws the following error:

Screenshot from 2019-08-01 21-45-25

The workaround right now is to include only the jitted methods in benchmarks.py. It is indicative of the extent of the speedup but isn't very accurate.

@canyon289
Copy link
Member

@Ban-zee Is this still an open issue?

@Ban-zee
Copy link
Contributor Author

Ban-zee commented Oct 4, 2019

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improvements to ArviZ Help Wanted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants