-
Notifications
You must be signed in to change notification settings - Fork 310
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
[REVIEW] BUG Move subcomms init outside of individual algorithm functions #1196
[REVIEW] BUG Move subcomms init outside of individual algorithm functions #1196
Conversation
…omms. Still have an issue with error stating comms not initialized when trying to init subcomms.
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
…o branch-0.16-movesubcomminit
…e_graph_container() call and using values obtained directly from handle instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides the comment about documentation, this looks good to me. Thank you for the quick fix!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much cleaner!
…on of get_n_workers() call, but still need FIXME for that addressed.
rerun tests |
Codecov Report
@@ Coverage Diff @@
## branch-0.16 #1196 +/- ##
==============================================
Coverage ? 57.28%
==============================================
Files ? 61
Lines ? 2500
Branches ? 0
==============================================
Hits ? 1432
Misses ? 1068
Partials ? 0
Continue to review full report at Codecov.
|
This PR moves the subcomms init outside of the individual algorithm functions and up to the function a user calls to initialize comms. This allows the same subcomm configuration to be used across algorithms and also allows users to customize the call to optimize based on GPU configuration.
Without this, subcomms will be repeatedly created/initialized for each algo call, resulting in problems.
closes #1065
(thanks to @Iroy30 for commits 71d4a0b and 79f131c)