Skip to content

[Frontend] [Core] Add Tensorizer support for LoRA adapter serialization and deserialization #17926

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
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

sangstar
Copy link
Contributor

@sangstar sangstar commented May 9, 2025

Serializing and deserializing LoRA adapters using tensorizer

This PR allows LoRA adapters to be serialized and deserialized using tensorizer. A test is added to confirm this and serializing LoRA files can be done with the same script that can save vLLM models in examples/tensorize_vllm_model.py.

Summary of changes

  • Adjusted the CLI args for .buildkite/test-pipeline.yaml's invocation of the tensorize_vllm_model.py example script to additionally save and load a LoRA adapter, testing a model generation after deserialization to confirm the LoRA adapter was loaded properly
  • Added --lora-path to tensorize_vllm_model.py as a base argparser argument that allows a user to specify the HuggingFace reference ID for a LoRA adapter, which can be either serialized or deserialized depending on whether the serialize or deserialize subparser is indicated.
  • Added test_serialize_and_deserialize_lora to test_tensorizer.py testing saving and loading LoRA adapters with tensorizer.
  • Allows deserializing a LoRA adapter by allowing TensorizerConfig to be passed in as a kwarg to LoRARequest. When this is done, the LoRA tensors are assumed to be in tensorizer's .tensors format and deserialized according to the parameters given in the TensorizerConfig provided.

Copy link

github-actions bot commented May 9, 2025

👋 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.

🚀

@mergify mergify bot added the documentation Improvements or additions to documentation label May 9, 2025
@jeejeelee jeejeelee self-assigned this May 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants