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.
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.
The current implementation using
_custom_function_callwill only return the device statistics from the first data-parallel head worker. This is because_custom_function_callis designed for scenarios where results from workers are either identical or can be merged like tensors. For device statistics, where each worker has unique information, this approach leads to loss of data from other workers.In a multi-worker environment, this would result in incomplete and potentially misleading statistics. A better approach is to explicitly gather the stats from all workers and return them as a list. This ensures that the caller receives a complete picture of the device status across the entire training setup.