-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Model] Add T5 model (2/2) #11901
base: main
Are you sure you want to change the base?
[Model] Add T5 model (2/2) #11901
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:
🚀 |
P.S I've tested in eager mode only so far, still have to investigate whether cuda graphing this one may cause issues or not |
This pull request has merge conflicts that must be resolved before it can be |
@NickLucche Thanks for implementing this PR! On testing your PR, I encountered some unexpected behaviors, and hope to get your insights on the problems Describe the issues:
In general, the output quality decreases when inferring by batches.
Steps to reproduce:
assert attn_bias is None # to be recomputed
The requests are sent using Python
tokenize_results = tokenizer(prompt, return_tensors="pt", padding= True, return_attention_mask= True)
input_ids, attn_mask = tokenize_results["input_ids"], tokenize_results["attention_mask"]
outputs = model.generate(input_ids= input_ids, attention_mask= attn_mask, do_sample= False, temperature= 0, top_k= 0, top_p= 0.0)
The full-
@NickLucche, do you have any insights into what might be causing the problems? |
Hey thanks a lot for giving it a spin! Are you able to observe the same behavior with Further testing with all params you've tried is surely needed, but the assert at https://github.com/NickLucche/vllm/blob/t5-model/vllm/model_executor/models/t5.py#L355 should not be removed. The fact that it raises on that condition is worth looking into on its own. |
I did a quick check by enabling the assertion in |
Thanks, that would match with the setup we currently have in tests. |
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Signed-off-by: NickLucche <nlucches@redhat.com>
Hey @vhminh2210 I could use your help to turn some of your experiments into unit tests to add. What models would you want to see tested? I am possibly looking for fine tuned T5 models, the base models such as |
Add support fot T5 (encoder-decoder model).
Follow-up and based on #11334, so it needs this other PR merged before it can be addressed, as it assumes to have a backend that supports passing a custom attention bias in both prefill and decode (xformers+pagedattention as of now).
Some topics I'd like to discuss here (RFC):
decoder_start_token_id
as it does for padding, but there's no explicit BOS. Current logic inpreprocess.py
would just crash. Is this the best approach to handle the quirk of T5?xformers.py
. I'd rather have spared this one, but it was assuming alibi_slopes were the only way to have multiple attention biases (one per sequence).Additional items: