GQA models have not supported prefix caching#2873
Closed
toslunar wants to merge 1 commit intovllm-project:mainfrom
Closed
GQA models have not supported prefix caching#2873toslunar wants to merge 1 commit intovllm-project:mainfrom
toslunar wants to merge 1 commit intovllm-project:mainfrom
Conversation
Collaborator
|
The issue was addressed by #3007 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I found a model that uses GQA returns wrong result with
prefix_pos. After some investigation, the code to support MQA/GQAvllm/vllm/model_executor/layers/attention.py
Lines 141 to 155 in 7e45107
, which repeats the inputs, is not compatible with the current implementation of prefix caching (
context_attention_fwd).To support MQA/GQA,
is closer, but KV of prefix should also be expanded (after they are read from
key_cacheandvalue_cache).