-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[Misc] Upgrade to pytorch 2.5 #9588
Conversation
👋 Hi! Thank you for contributing to the vLLM project. Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can do one of these:
🚀 |
/ready |
@@ -4,7 +4,7 @@ | |||
# Dependencies for NVIDIA GPUs | |||
ray >= 2.9 | |||
nvidia-ml-py # for pynvml package | |||
torch == 2.4.0 | |||
torch == 2.5.0 |
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.
Only concern here is now torch==2.5.0
uses the 12.4 cuda
bindings by default. We might want to update the installation docs (including on the readme) to alert users that they may want to pass --extra-index-url https://download.pytorch.org/whl/cu121
during installation depending on the machine they are using
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.
@robertgshaw2-neuralmagic Does this mean that there would need to be multiple vllm packages (one for 12.1 and one for 12.4)? Or should I try to install pytorch 2.5 built with 12.1 (if such a thing exists)?
@bnellnm it loos like there are some cmake errors:
the cuda version should not matter that much. I think our current pipeline should still work even if pytorch itself is built against cuda 12.4 . |
Looks related to #8609 |
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com>
endif() | ||
target_link_libraries(${GPU_MOD_NAME} PRIVATE ${CUDA_CUDA_LIB} | ||
${CUDA_LIBRARIES}) | ||
target_link_libraries(${GPU_MOD_NAME} PRIVATE CUDA::cudart CUDA::cuda_driver) |
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.
Nice!
pyproject.toml
Outdated
@@ -6,7 +6,7 @@ requires = [ | |||
"packaging", | |||
"setuptools>=61", | |||
"setuptools-scm>=8.0", | |||
"torch == 2.4.0", | |||
"torch == 2.5.0 --extra-index-url https://download.pytorch.org/whl/cu121", |
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.
Given @youkaichao's comment:
the cuda version should not matter that much. I think our current pipeline should still work even if pytorch itself is built against cuda 12.4 .
We should consider ditching the --extra-index-url
. Perhaps this should be configurable, but one thing to note is that 2:4 sparse fp8 will require the Pytorch version that's built with 12.4
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.
The PR looks good but we should quickly come to a consensus on what to do with the CUDA version that pytorch is built against
Im fine to remove the |
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com>
Please merge from main to fix the CI failures for multi-modal models. |
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.
excited to see it happen!
Signed-off-by: youkaichao <youkaichao@gmail.com>
some errors are real:
fixing by 0068133 |
pytorch 2.5 changes the output slightly:
The output is still sensible. Therefore I changed it to logprobs check instead. For future reference, we can also change to logprobs check if exact comparison is not feasible while it is not our fault (due to pytorch or huggingface numerical change). |
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: Shanshan Wang <shanshan.wang@h2o.ai>
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: Shanshan Wang <shanshan.wang@h2o.ai>
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: qishuai <ferdinandzhong@gmail.com>
Hi, looking forward to this new support, I wonder when will it be released? Thanks! |
This reverts commit 3cb07a3.
you can install the wheel from main branch to use it directly. see https://docs.vllm.ai/en/latest/getting_started/installation.html#install-the-latest-code |
@youkaichao thanks! but is it less stable than a stable version? |
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: Randall Smith <Randall.Smith@amd.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: Bill Nell <bill@neuralmagic.com> Signed-off-by: youkaichao <youkaichao@gmail.com> Co-authored-by: youkaichao <youkaichao@gmail.com> Signed-off-by: NickLucche <nlucches@redhat.com>
Upgrade to pytorch 2.5
Requires changes to flash attn: vllm-project/flash-attention#23
PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:
[Bugfix]
for bug fixes.[CI/Build]
for build or continuous integration improvements.[Doc]
for documentation fixes and improvements.[Model]
for adding a new model or improving an existing model. Model name should appear in the title.[Frontend]
For changes on the vLLM frontend (e.g., OpenAI API server,LLM
class, etc.)[Kernel]
for changes affecting CUDA kernels or other compute kernels.[Core]
for changes in the core vLLM logic (e.g.,LLMEngine
,AsyncLLMEngine
,Scheduler
, etc.)[Hardware][Vendor]
for hardware-specific changes. Vendor name should appear in the prefix (e.g.,[Hardware][AMD]
).[Misc]
for PRs that do not fit the above categories. Please use this sparingly.Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:
format.sh
to format your code.docs/source/
if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.
Tensors
require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.torch.libary.opcheck()
to test the function registration and meta-function for any registered ops. Seetests/kernels
for examples.Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with
rfc-required
and might not go through the PR.What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:
action-required
label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.Thank You
Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!