-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[RFC] Introduce Strategy
in favor of TrainingTypePlugin
#10549
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
Comments
Yes, definitely. We agreed on this I think. This was already set in motion by the introduction of the strategy argument in the Trainer.
Has to be done for 1.6. We are targeting stable API for these components at 1.6. |
Should we name all classes without the "Plugin"/"Strategy" suffix? Here is how this would look like: DataParallel, (or just DP) |
On naming, Loggers, Profilers, Accelerators, and ClusterEnvironments are suffixed with the component name (e.g. TensorboardLogger, SimpleProfiler, GPUAccelerator, SlurmEnvironment). If we drop the suffix for strategy:
|
Proposed plan:
Step 3) is necessary because of certain usages of these plugins, even when they are not being subclassed. One example is: More follow-ups will include:
|
StrategyPlugin
in favor of TrainingTypePlugin
Strategy
in favor of TrainingTypePlugin
Summary: DDPPlugin has been renamed to DDPStrategy (as part of Lightning-AI/pytorch-lightning#10549), causing oss CI to fail. Simply skipping the import to unblock CI since DDP feature is not used in test. Differential Revision: D33351636 fbshipit-source-id: 76c751725b05bc818fb1c4b18e8d064fca71bc18
Summary: DDPPlugin has been renamed to DDPStrategy (as part of Lightning-AI/pytorch-lightning#10549), causing oss CI to fail. Simply skipping the import to unblock CI since DDP feature is not used in test. Reviewed By: kazhang Differential Revision: D33351636 fbshipit-source-id: 7a1881c8cd48d9ff17edd41137d27a976103fdde
We also have to remember to rename the test files and test names that include the word plugin. |
I could take care of it. |
Closing this issue, as the Strategy transition has been completed! Thank you to everyone involved ❤️ |
Uh oh!
There was an error while loading. Please reload this page.
Proposed refactor
Part of #9932
Related PR: #10548
Motivation
As we are introducing
StrategyPlugin
in favor ofTrainingTypePlugin
for this release.@ananthsub raised some really good points for discussion regarding
StrategyPlugin
. ReferenceProposed solution
Three main points to be discussed here
Plugin
from the name of the classpytorch_lightning/strategy
directoryDDPStrategy
and so on.Would like your thoughts? @PyTorchLightning/core-contributors
cc @Borda @justusschock @awaelchli @akihironitta @kaushikb11 @ananthsub
The text was updated successfully, but these errors were encountered: