Add barriers after init_process_group() for all recipes #5475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently only the detection recipe supports this:
vision/references/detection/utils.py
Lines 278 to 281 in d367a01
Adding barriers to all other recipes.
@mrshenli clarified offline that in theory, we shouldn't need that, as init_process_group already performed a store-based barrier (see here). The dist.barrier is basically an empty allreduce. But to be on the safe side, we opted for adding this in all references.