Skip to content

[Core] Add reload_weights RPC method #20096

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

Merged
merged 8 commits into from
Jul 23, 2025

Conversation

22quinn
Copy link
Collaborator

@22quinn 22quinn commented Jun 25, 2025

Essential Elements of an Effective PR Description Checklist

  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

See #19886

Test Plan

See #19640

Test Result

See #19640

(Optional) Documentation Update

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @22quinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces the core functionality for a new reload_weights RPC method, enabling the dynamic, in-place reloading of model weights for both GPU and TPU workers. This change refactors existing model loading logic to clearly separate initial model loading from subsequent weight reloading, and it includes improvements to memory pool context management.

Highlights

  • Support for reload_weights RPC: Core reload_weights methods have been added to GPUModelRunner and TPUModelRunner to facilitate in-place reloading of model weights, laying the groundwork for an RPC method.
  • Worker-level exposure: The new reload_weights functionality is exposed at the GPUWorker and TPUWorker levels, allowing higher-level components to trigger weight reloads.
  • Refactored model loading: The load_model methods in GPUModelRunner and TPUModelRunner have been simplified to always perform a full model load, removing the previous conditional in-place weight reloading logic.
  • Memory pool context helper: A new private helper method _maybe_get_memory_pool_context was introduced in GPUWorker to centralize and simplify the management of memory pool contexts during model and KV cache operations.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added v1 tpu Related to Google TPUs labels Jun 25, 2025
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a reload_weights RPC method, which is a valuable addition for dynamically updating model weights. The implementation is clean and consistent across both GPU and TPU workers. The refactoring of load_model to separate concerns is a good design choice, and the consolidation of memory pool context logic in the GPU worker improves code quality.

My main feedback is on a potential side effect of the load_model refactoring in gpu_model_runner.py, which now always reloads the model from scratch. This changes its previous behavior and might affect existing callers or tests that expect an in-place weight reload. Please see the detailed comment on this.

Signed-off-by: 22quinn <[email protected]>
Signed-off-by: 22quinn <[email protected]>
Copy link

mergify bot commented Jun 28, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @22quinn.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Jun 28, 2025
Signed-off-by: 22quinn <[email protected]>
@mergify mergify bot removed the needs-rebase label Jun 29, 2025
Signed-off-by: 22quinn <[email protected]>
@22quinn 22quinn added the ready ONLY add when PR is ready to merge/full CI is needed label Jul 17, 2025
Copy link
Collaborator

@houseroad houseroad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment, otherwise, looks good to me.

@@ -1192,6 +1186,11 @@ def load_model(self) -> None:
self.model = model
self.sampler = TPUSampler()

def reload_weights(self) -> None:
model_loader = get_model_loader(self.load_config)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can we have a sanity check that model is loaded already?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@houseroad good call. Added an assertion and a corresponding unit test

Copy link

mergify bot commented Jul 18, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @22quinn.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Jul 18, 2025
Signed-off-by: 22quinn <[email protected]>
@mergify mergify bot removed the needs-rebase label Jul 18, 2025
@houseroad houseroad enabled auto-merge (squash) July 18, 2025 23:48
Copy link

mergify bot commented Jul 19, 2025

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @22quinn.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

@mergify mergify bot added the needs-rebase label Jul 19, 2025
auto-merge was automatically disabled July 19, 2025 05:36

Head branch was pushed to by a user without write access

@mergify mergify bot removed the needs-rebase label Jul 19, 2025
@simon-mo simon-mo merged commit 5c9b807 into vllm-project:main Jul 23, 2025
62 of 65 checks passed
LyrisZhong pushed a commit to LyrisZhong/vllm that referenced this pull request Jul 23, 2025
self.model_runner.load_model(eep_scale_up=eep_scale_up)

def update_config(self, overrides: dict[str, Any]) -> None:
self.model_runner.update_config(overrides)

def reload_weights(self) -> None:
with self._maybe_get_memory_pool_context(tag="weights"):
Copy link

@hydrozhao hydrozhao Jul 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should delete this line? Because the precondition of reload_weights is that params are already created and memory pool is not reentrant.

image

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If using the default loader below, new params are not created, but it's dependent on individual model's load_weights implementation? cc @youkaichao @ywang96 do you feel appropriate to remove?

def default_weight_loader(param: torch.Tensor,
loaded_weight: torch.Tensor) -> None:
"""Default weight loader."""
try:
if param.numel() == 1 and loaded_weight.numel() == 1:
# Sometimes scalar values aren't considered tensors with shapes
# so if both param and loaded_weight are a scalar,
# "broadcast" instead of copy
param.data.fill_(loaded_weight.item())
else:
assert param.size() == loaded_weight.size(), (
f"Attempted to load weight ({loaded_weight.size()}) "
f"into parameter ({param.size()})")
param.data.copy_(loaded_weight)

avigny pushed a commit to avigny/vllm that referenced this pull request Jul 31, 2025
wenscarl pushed a commit to wenscarl/vllm that referenced this pull request Aug 4, 2025
x22x22 pushed a commit to x22x22/vllm that referenced this pull request Aug 5, 2025
Pradyun92 pushed a commit to Pradyun92/vllm that referenced this pull request Aug 6, 2025
npanpaliya pushed a commit to odh-on-pz/vllm-upstream that referenced this pull request Aug 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready ONLY add when PR is ready to merge/full CI is needed tpu Related to Google TPUs v1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants