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
vbench for statsmodels #936
Comments
I can look into vbench. Will need a bit of time. |
I could also give it a shot in a few weeks. Do you have any experience with it @vincentarelbundock? I started to setup a version for a project I'm working on and gave up after an hour or so. If I do take it on I'll write up some docs for future statsmodels devs and perhaps push those upstream to vbench. They are sorely sparse/nonexistent :-) Either way, the project could be broken into parts. There's this issue of setting up the framework, and then there's the actual writing of the benchmarks. I'd be happy to help in either pace. |
No experience here. Go ahead if you feel like it. Little experience is better than no experience. |
Ok thanks. Like I said, it will be a few weeks. |
@vincentarelbundock @TomAugspurger Thank you, that would be great. I don't know anything about setting up a vbench, I was just following Yarik a bit who set up a vbench for numpy and it looks very useful. I can also help with the benchmarks. |
Ok. As I'm going through I'll note down the unix/windows idiosyncrasies. |
I think we can try to host the results from the vbench runs on gh-pages. I started a new repo and a dummy page I still haven't tried to run the vbench on Windows. |
Why not use sourceforge for hosting with the rest of the docs? |
no special reason for not using sourceforge, except I thought it will be easier to The only problem I see is that we will have to purge the git history sometimes to prevent it from getting too large. |
Push is just a |
Closed by https://github.com/statsmodels/vbench |
statsmodels still doesn't have a vbench for performance monitoring.
One target for statsmodels 0.6 could be to look for performance improvements, and check whether some previous changes caused serious performance regressions.
some references
https://github.com/pydata/vbench/tree/master/vbench
https://github.com/pydata/pandas/tree/master/vb_suite
https://github.com/yarikoptic/numpy-vbench
The text was updated successfully, but these errors were encountered: