-
Notifications
You must be signed in to change notification settings - Fork 668
Fix quantization with generate #1784
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1784
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit dd5ae32 with merge base 27b0fcc ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@@ -366,7 +366,7 @@ def generate( | |||
tokens, logits = custom_generate_next_token( | |||
model, | |||
input_pos=curr_input_pos, | |||
x=tokens, | |||
x=tokens.clone(), |
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.
This is needed as cudagraphs is complaining about tensors being overwritten from previous graphs.
can i ask a question ? @SalmanMohammadi Why is the inference speed of the quantized model so slow? |
Context
What is the purpose of this PR? Is it to
Please link to any issues this PR addresses.
Closes #1775
This branch means generate is no longer erroring out with quantized models. However, there is something funky going on as generation with quantized models uses more memory (~17GB vs ~16GB) and is significantly slower (4.5 toks/s vs 25 toks/s).
First quantizing the model:
Now, on main trying generate:
On this branch
Test plan
Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.
pre-commit install
)pytest tests
pytest tests -m integration_test
UX
If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example