-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[Lora] Support long context lora #4787
[Lora] Support long context lora #4787
Conversation
vllm/lora/layers.py
Outdated
@@ -1193,3 +1203,204 @@ def can_replace_layer(cls, source_layer: nn.Module, | |||
model_config: Optional[PretrainedConfig]) -> bool: | |||
# Special handling for the LogitsProcessor. | |||
return False | |||
|
|||
|
|||
class LoRALinearScalingRotaryEmbedding(LinearScalingRotaryEmbedding): |
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.
not needed
vllm/lora/layers.py
Outdated
return query, key | ||
|
||
|
||
class LoRAPagedAttentionWithRoPE(LoRALayer): |
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.
not needed
tests/lora/conftest.py
Outdated
@@ -21,6 +21,41 @@ | |||
from vllm.model_executor.layers.vocab_parallel_embedding import ParallelLMHead | |||
from vllm.model_executor.model_loader import get_model | |||
|
|||
LONG_LORA_INFOS = [ |
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.
Will be moved to hf hub
tests/lora/test_long_context.py
Outdated
) | ||
return lora_llm | ||
|
||
def test_batched_rope_kernel(self, long_context_infos): |
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.
currently this test has illegal memory access
The PR is ready to be reviewed |
tests failing? |
that' expected because we need to move fine tuned lora model to hf hub so that CI can access it. will be done soon. The test succeeds locally. |
Use hf instead of s3 now |
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.
@Yard1 compared to internal version;
- clean up on some of variables and logic
- Added a test to test_layers.py
- Replaced rotary embedding instead of self.attn
- fixed a bug where rotary emb is only replacing the first layer
- download lora fine tuned models from hf hub I created
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.
Thanks, looks good! Some small comments
vllm/core/scheduler.py
Outdated
prompt_limit = (seq_group.lora_request.long_lora_max_len | ||
if seq_group.lora_request | ||
and seq_group.lora_request.long_lora_max_len else | ||
self.prompt_limit) |
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.
let's put it in a method/function
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.
removed self.prompt_limit btw because in this case, it doesn't make much sense to have it.
tests/lora/test_lora_checkpoints.py
Outdated
@@ -28,6 +28,7 @@ def test_load_checkpoints( | |||
# and the test should pass. | |||
LoRAModel.from_local_checkpoint( | |||
baichuan_lora_files, | |||
4096, |
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.
use kwarg instead
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.
Default None == meaning it will use scaling factor 1. Also added docstring
@Yard1 everything addressed |
Currently we need to call rotary embedding kernel for each LoRA, which makes it hard to serve multiple long context length LoRA. Add batched rotary embedding kernel and pipe it through. It replaces the rotary embedding layer to the one that is aware of multiple cos-sin-cache per scaling factors. Follow up of https://github.com/vllm-project/vllm/pull/3095/files
Currently we need to call rotary embedding kernel for each LoRA, which makes it hard to serve multiple long context length LoRA. Add batched rotary embedding kernel and pipe it through. It replaces the rotary embedding layer to the one that is aware of multiple cos-sin-cache per scaling factors. Follow up of https://github.com/vllm-project/vllm/pull/3095/files
May I ask a question? Only LinearScalingRotaryEmbedding requires the 'withlora' version. Do DynamicNTKScalingRotaryEmbedding/YaRNScalingRotaryEmbedding/Phi3SuScaledRotaryEmbedding also require it? |
I think those are not working with long context multi lora. In order to get it working, I think other rotary embedding should also support multi scaling factors like we are doing for |
ok, thanks for your response :) |
Currently we need to call rotary embedding kernel for each LoRA, which makes it hard to serve multiple long context length LoRA. Add batched rotary embedding kernel and pipe it through. It replaces the rotary embedding layer to the one that is aware of multiple cos-sin-cache per scaling factors. Follow up of https://github.com/vllm-project/vllm/pull/3095/files
Currently we need to call rotary embedding kernel for each LoRA, which makes it hard to serve multiple long context length LoRA. Add batched rotary embedding kernel and pipe it through.
It replaces the rotary embedding layer to the one that is aware of multiple cos-sin-cache per scaling factors.
Follow up of https://github.com/vllm-project/vllm/pull/3095/files
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.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!