-
Notifications
You must be signed in to change notification settings - Fork 21
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
Optimize ArbitraryMotion #396
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #396 +/- ##
==========================================
- Coverage 89.47% 89.25% -0.23%
==========================================
Files 43 44 +1
Lines 2728 2727 -1
==========================================
- Hits 2441 2434 -7
- Misses 287 293 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
|
By the moment, I just got rid of the
With this changes, I executed the example below:
In master brach: Now: Maybe that is enough improvement and we do not need to consider re-using the weights (in fact, I think this does it internally) I should do more tests during these days |
I created a new branch optimize-arbitrary-parallel in which I initialize the interpolation functions and store them in the |
A new branch, optimize-arbitrary-view, was created. This branch initializes the interpolating functions directly in GPU, so CPU-GPU transfers are not needed for this now. The performance is even better, although with a bit more allocations than optimize-arbitrary-parallel:
In addition, a custom adapt function for ArbitraryMotion is not needed now. Maybe this can solve problems in #405 and #406. My branch has not included the changes from these last two PRs from @rkierulf yet, so maybe I will need to change something once this is done. In short, since optimize-arbitrary-view is by far the preferred option, I will close this PR and open a new one with this branch: #408 |
This PR is intended to address #371 and #372