-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[FP8] Extend per-token-group quantization support to QuantFP8 #24342
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
Merged
+444
−61
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b0b9d48
add per-token-group quantization support to QuantFP8
tahsintunan 74bd084
Update vllm/model_executor/layers/quantization/utils/quant_utils.py
tahsintunan b50d163
Add PyTorch implementation for QuantFP8 group quantization
tahsintunan 2662be1
refactor: move FP8 quantization functions into QuantFP8
tahsintunan 4fe4578
Refactor benchmark to support all group shapes
ProExpertProg 100b11c
refactor: clean up QuantFP8 forward methods and consolidate tests
tahsintunan dd45227
refactor: test_fp8_quant_group to avoid mypy type errors
tahsintunan ff0855a
bench: add CLI args for FP8 benchmark configuration
tahsintunan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Why aren't we compiling with dynamic=True? I don't think we should be targeting shape specialization since we won't use that in practice
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.
In practice we specialize on all shapes except the first dim (
num_tokens
). Thewith_dyn_arg
marks that shape as dynamic to fully simulate vLLM usage 👍