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

automate benchmarking #2

Closed
orbeckst opened this issue Dec 6, 2017 · 5 comments
Closed

automate benchmarking #2

orbeckst opened this issue Dec 6, 2017 · 5 comments
Assignees

Comments

@orbeckst
Copy link
Member

orbeckst commented Dec 6, 2017

Performance benchmarking should be run continuously.

Current plan

  • use a CRON job on c3potato.beckstein.physics.asu.edu
  • publish benchmark data in this repo in the master branch
  • publish benchmark html/js in this repo in the gh-branch (which shows up as https://www.mdanalysis.org/benchmarks/)

Background

@orbeckst orbeckst self-assigned this Dec 6, 2017
@orbeckst
Copy link
Member Author

orbeckst commented Dec 6, 2017

Note that astropy does something clever (or confusing): the master branch are the actual benchmark tests (our mdanalysis/benchmarks), the results branch contains results (our benchmarks master), and any commits to their result branch trigger Travis, which automatically deploys the asv web site page to the gh-pages branch.

@orbeckst
Copy link
Member Author

It would be useful if the automated benchmarks did not re-run benchmarks that were already run. Ideally,

  • recognize commits that have not been benchmarked and only run those
  • recognize benchmarks that have not been run and only run those

@orbeckst
Copy link
Member Author

Possibly use --skip-existing (from asv run --help):

  --skip-existing-successful
                        Skip running benchmarks that have previous successful
                        results
  --skip-existing-failed
                        Skip running benchmarks that have previous failed
                        results
  --skip-existing-commits
                        Skip running benchmarks for commits that have existing
                        results
  --skip-existing, -k   Skip running benchmarks that have previous successful
                        or failed results

@orbeckst
Copy link
Member Author

Or use (see https://asv.readthedocs.io/en/latest/using.html )

asv run NEW

You can benchmark all commits since the last one that was benchmarked on this machine. This is useful for running in nightly cron jobs:

@orbeckst
Copy link
Member Author

crontab is running daily 3:30am AZ = 10:30 GMT so results should become available a few minutes to a few hours later (depending on how many new commits/benchmarks were added).

If something is not working properly, please open an issue.

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

Successfully merging a pull request may close this issue.

1 participant