-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[optim][adamw] default to foreach when CUDA + differentiable=False #92306
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
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/92306
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit b78c9b2: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
albanD
left a comment
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.
SGTM
…le=False" cc ezyang gchanan [ghstack-poisoned]
…le=False" cc ezyang gchanan [ghstack-poisoned]
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Stack from ghstack (oldest at bottom):
cc @ezyang @gchanan
BC-breaking note
Algorithms
{Adadelta, Adagrad, Adam, Adamax, AdamW, ASGD, NAdam, RAdam, RMSProp, RProp, SGD}default to fasterforeachimplementation when on CUDA + differentiable=FalseWhen applicable, this changes the default behavior of
step()and anything that calls intoadadelta(...),adagrad(...),adam(...),adamax(...),adamw(...),asgd(...),nadam(...),radam(...),rmsprop(...),rprop(...),sgd(...)directly to use theforeachimplementation instead of the for-loop for better performance. Applicable meansforeach,fused, ordifferentiable),torch.jit.is_scriptingisFalse.When these conditions are satisfied, the implementation used will match the implementation used when one passes
foreach=True. The user defined flag forforeachwill NOT be overwritten in order to preserve user selections. For more details, check the documentation. There should be no significant differences between the results returned by these optimizers. To revert to the old behavior, say, foradam, pass inadam(..., foreach=False, ...)or initializeAdamwithAdam(..., foreach=False, ...).