Deprecate LightningDistributed and keep broadcast in ddp/ddpSpawn directly #9692
Labels
deprecation
Includes a deprecation
distributed
Generic distributed-related topic
feature
Is an improvement or enhancement
refactor
Uh oh!
There was an error while loading. Please reload this page.
Proposed refactoring or deprecation
LightningDistributed() class only used by ddp and ddpSpawn, and only have one broadcast function for torch collectives. It's unnecessary to have.
Also, we have to set rank and device in set up steps. If subclass extend DDP or DDPSpawn, and overridden function where LightningDistributed.rank and device setted, could cause silent failures.
Motivation
Simplify the code structure and reduce the possibilities for silent failure
Pitch
Deprecate LightningDistributed. There is only one function
Move to ddp and ddpSpawn
Additional context
Related to #7534
If you enjoy Lightning, check out our other projects! ⚡
Metrics: Machine learning metrics for distributed, scalable PyTorch applications.
Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, finetuning and solving problems with deep learning
Bolts: Pretrained SOTA Deep Learning models, callbacks and more for research and production with PyTorch Lightning and PyTorch
Lightning Transformers: Flexible interface for high performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.
The text was updated successfully, but these errors were encountered: