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

Use airspeed velocity for benchmarking #8361

Closed
cpcloud opened this issue Sep 22, 2014 · 1 comment · Fixed by #9715
Closed

Use airspeed velocity for benchmarking #8361

cpcloud opened this issue Sep 22, 2014 · 1 comment · Fixed by #9715
Labels
Performance Memory or execution speed performance Testing pandas testing functions or related to the test suite
Milestone

Comments

@cpcloud
Copy link
Member

cpcloud commented Sep 22, 2014

Since vbench was (at least in part) an inspiration for Airspeed Velocity (asv), I think getting something like this set up for pandas would be useful and extremely helpful for us and for asv. We have a ton of vbench code and we'd probably be a great project for pushing the boundaries of and finding edge cases in asv. This would also be a great for someone to get to know the scale of datasets for which pandas was designed.

Here's a nice demo of astropy using asv: http://mdboom.github.io/astropy-benchmark

@cpcloud cpcloud added Performance Memory or execution speed performance Testing pandas testing functions or related to the test suite labels Sep 22, 2014
@jreback jreback added this to the 0.16 milestone Sep 22, 2014
@jreback jreback modified the milestones: 0.16, 0.15.1 Oct 7, 2014
@jreback jreback modified the milestones: 0.16.0, Next Major Release Mar 6, 2015
@jorisvandenbossche
Copy link
Member

Apparently @qwhelan did already some work on this: airspeed-velocity/asv#194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Performance Memory or execution speed performance Testing pandas testing functions or related to the test suite
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants