-
Notifications
You must be signed in to change notification settings - Fork 296
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
add profiling using cprofile #644
base: masterr
Are you sure you want to change the base?
Conversation
|
So looking things over the speed bottlenecks on functions are generally where you would expect. For instance, on |
Using This was for generating 400 time steps into the future without a GPU. For a longer sequence maybe that would be faster? In general though I don't think the torch.compile is worth the potential problems with losing the confidence interval that might come with it. |
|
|
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #644 +/- ##
===========================================
- Coverage 75.79% 64.59% -11.20%
===========================================
Files 67 67
Lines 4846 4850 +4
===========================================
- Hits 3673 3133 -540
- Misses 1173 1717 +544
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 17 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
The goal of this PR is add automatic optimization/time calculation metrics. Also maybe do some optimization of some the code and find out where it does not run efficiently.