-
Notifications
You must be signed in to change notification settings - Fork 5
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
Improve test suite execution speed #42
Comments
Caching dependencies: experiment notesComparison of various options I've tried for caching dependencies. Nb. we can see & manage caches via UI: https://github.com/dsgibbons/shap/actions/caches Repository caches limited to 10GB. Timings
Approaches0. BaselineExisting approach, just pip-install with no caching. 1. Enable cache in the setup python action.Caches the wheels, but not the installed environment. As per the action docs.
2. Cache the whole python envAs per this blog
3. Cache specific libraries in site-packagesCache only the libraries which need to be built, such as pyspark. Leave other libs to be pip-installed as before To decide which packages to cache: we want to save the most time, whilst keeping under ~2GB total cache size per env. Some calculations from experimentation, sorted by those that save the most time for the least space:
So, decide to cache just the first 3 libraries. In future if we drop support for any python versions, we can cache more libraries. Implementing options on PR #84 . |
Ported to shap#3045 |
I think there are a few areas for improvement in the GitHub test suite that we could address to improve the execution speed. Currently the unit tests take almost 20 minutes to run on CI. If we could reduce that it could help reduce the time it takes to validate PRs, improving our effectiveness as reviewers.
TODO
Slowest tests
[Updated] here are the current set of slowest tests:
The text was updated successfully, but these errors were encountered: