Use root_device
in DeviceStatsMonitor callback
#11748
Merged
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.
Minor refactor to use the strategy's own
root_device
instead of the LightningModule's device property.Attempts at manual model parallelization will face difficulties with the assumption that the LightningModule has a well-defined
device
property. Not all of the model parameters will be on the same device.For those use cases, it is critical to remove the assumption that the module has a device property (device on the module in general goes against PyTorch's design principles:
device
attribute pytorch/pytorch#7460What does this PR do?
Does your PR introduce any breaking changes? If yes, please list them.
No
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃
cc @Borda @justusschock @awaelchli @akihironitta @rohitgr7 @kaushikb11