-
Notifications
You must be signed in to change notification settings - Fork 25.4k
[TP] Add deprecation warnings in the documentations for Pairwise parallel, sequence parallel and other prepare input/output functions #111176
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/111176
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 9f3b9d7 with merge base 35750bf ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
looks good
… parallel and other prepare input/output functions" As part of TP UX improvements, we want to keep our API simple (not easy) so that users get the flexibility to do what they want and avoid a too generic API which tries to solve everything and get things too complicated. We are updating the doc accordingly. [ghstack-poisoned]
… parallel and other prepare input/output functions" As part of TP UX improvements, we want to keep our API simple (not easy) so that users get the flexibility to do what they want and avoid a too generic API which tries to solve everything and get things too complicated. We are updating the doc accordingly. [ghstack-poisoned]
… parallel and other prepare input/output functions" As part of TP UX improvements, we want to keep our API simple (not easy) so that users get the flexibility to do what they want and avoid a too generic API which tries to solve everything and get things too complicated. We are updating the doc accordingly. [ghstack-poisoned]
https://docs-preview.pytorch.org/pytorch/pytorch/111176/distributed.tensor.parallel.html looks like prepare input/outout docs still have issues |
@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 |
@fduwjj This is not related to deprecation warning, see here https://docs-preview.pytorch.org/pytorch/pytorch/111176/distributed.tensor.parallel.html#torch.distributed.tensor.parallel.style.PrepareModuleOutput The examples in the doc are not properly formatted |
We see use cases where embedding sharding is also needed in TP API so we enabled it in the API since DTensor already support colwise embedding sharding. Pull Request resolved: #111177 Approved by: https://github.com/wanchaol ghstack dependencies: #111160, #111166, #111176
…llel, sequence parallel and other prepare input/output functions (pytorch#111176) As part of TP UX improvements, we want to keep our API simple (not easy) so that users get the flexibility to do what they want and avoid a too generic API which tries to solve everything and get things too complicated. We are updating the doc accordingly. Pull Request resolved: pytorch#111176 Approved by: https://github.com/wanchaol ghstack dependencies: pytorch#111160, pytorch#111166
We see use cases where embedding sharding is also needed in TP API so we enabled it in the API since DTensor already support colwise embedding sharding. Pull Request resolved: pytorch#111177 Approved by: https://github.com/wanchaol ghstack dependencies: pytorch#111160, pytorch#111166, pytorch#111176
Pull Request resolved: pytorch#111346 Approved by: https://github.com/wanchaol ghstack dependencies: pytorch#111160, pytorch#111166, pytorch#111176, pytorch#111177
Stack from ghstack (oldest at bottom):
As part of TP UX improvements, we want to keep our API simple (not easy) so that users get the flexibility to do what they want and avoid a too generic API which tries to solve everything and get things too complicated. We are updating the doc accordingly.