Repository navigation
[PyTorch-MPS] Pin nightly Torch for earlier GPU submission #1117
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
Open
WindChimeRan
wants to merge
2
commits into
vllm-project:main
Choose a base branch
from
WindChimeRan:ran/pytorch-nightly-mps-submission
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| # Override vLLM's Torch pin for upstream MPS submission improvements: | ||
| # https://github.com/pytorch/pytorch/pull/200181 | ||
| --extra-index-url https://download.pytorch.org/whl/nightly/cpu | ||
| torch==2.16.0.dev20261013 | ||
| torchvision==0.30.0.dev20261013 | ||
| torchaudio==2.11.0.dev20261013 |
Oops, something went wrong.
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.
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.
Should we keep vLLM 0.31’s Torch 2.13 default and make this nightly stack an explicit PyTorch-MPS opt-in? My concern is that it overrides the supported stack for every install, while the measured gain is MPS-only.
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.
I also don't want to over-complicates UX - Users should not be expected to memorize or search for how to install these correctly. homebrew should be the default setting for most users.
Right now the pytorch-mps is still experimental. I plan to mark it as "usable" once there is one feature better than mlx path (such as the Qwen3-TTS, waiting for upstream merge now). So I marked this PR as draft, it's a bit overkill for now without real benefits.
Eventually I want the user just homebrew install, then they can run all features. currently tts and gguf are not in the homebrew path, so I opened #1161 .
After upstream omni PR merged, I'll run more tests on if we can bring pytorch-mps, nightly wheel, omni to the default installation (if the dependency cost is small, and the performance & UX gain are big)
Uh oh!
There was an error while loading. Please reload this page.
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.
MLX path throughput is unchanged, mainly because it's in low coupling with pytorch (we only use it for scheduler, meta data bookkeeping and some sampling fallbacks):
Qwen3-0.6B, 100 requests per setting, 1,024 input/128 output tokens.