-
Notifications
You must be signed in to change notification settings - Fork 10
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
Benchmarking and improving HMC/NUTS #19
Comments
PS. perhaps we should link back to the commit as well. |
Link to Benchmark spread sheet |
I wonder if there is a GitHub service like Travis does this. |
It's possible to perform these benchmarking using Travis, by running each task in a separate stage. For example
All these runtime ratios can be automatically posted into PR comments (Mohamed already implemented this in Fully supporting this idea still requires some work. I think we can solve this issue after |
I'm aware of that. Just wonder if there is an off-the-shelf GitHub service like that. |
This feature will be added to |
Guys do you need help to transfer Travis stuff to GitHub Actions? |
I suggest that we use this issue as an umbrella page for tracking improvements of benchmarking performances (memory, running time). For every new commit, we could write a small julia script to automatically (see GitHub.jl) post a new comment to this issue containing updated runtime information.
Related issues:
ForwardDiff.gradient
is slowForwardDiff.gradient
is slow Turing.jl#234The text was updated successfully, but these errors were encountered: