https://github.com/stan-dev/performance-tests-cmdstan
Performance testing tools for use with CmdStan
https://github.com/stan-dev/performance-tests-cmdstan
Last synced: 6 months ago
JSON representation
Performance testing tools for use with CmdStan
- Host: GitHub
- URL: https://github.com/stan-dev/performance-tests-cmdstan
- Owner: stan-dev
- Created: 2018-03-30T02:54:05.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2025-07-10T03:47:40.000Z (7 months ago)
- Last Synced: 2025-07-18T15:36:47.048Z (6 months ago)
- Language: Python
- Size: 659 KB
- Stars: 7
- Watchers: 7
- Forks: 8
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# performance-tests-cmdstan
Performance testing tools for use with CmdStan
## "Install"
```
git clone --recursive https://github.com/stan-dev/performance-tests-cmdstan.git
```
## Test performance in current working directory
To test the performance of the current cmdstan et al working directory on, for example, @betanalpha's stat_comp_benchmarks model repo, you can run the following:
```
./runPerformanceTests.py -j8 stat_comp_benchmarks
```
`./runPerformanceTests.py --help` for more options.
## Cleaning
`make clean` will recursively remove all non-checked-in files from all submodules. `make revert` will bring cmdstan and its submodules back to the commit specified by the current commit of the top-level `performance-tests-cmdstan` repo.
## Testing one git commit against another
to test e.g. develop against a branch you've made on cmdstan,
```
./compare-git-hashes.sh "stat_comp_benchmarks -j8 --runs 10 "
```
All of these take pull request numbers, so to test stan-dev/math#1244 against develop (for example) you can run:
```
./compare-git-hashes.sh example-models/bugs_examples/vol2/schools/ develop develop false d013e55
```
Here the false could be replaced with `develop` - just says to use the Stan hash associated with the CmdStan hash, in this case `develop`.
The script will then check out and pull all of these commits, branches, or PRs from stan-dev. It should print out which commit hashes it ends up on; please check that these are correct as the script is new. For PRs, you will see an unfamiliar hash that GitHub creates to store the result of the merge of the PR into the base branch the PR is against.