-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
[Attention][TurboQuant] Share dequant buffers, eliminate float16_copy #40941
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
DarkLight1337
merged 4 commits into
vllm-project:main
from
bhoomit:turboquant-backend-optimizations
Apr 27, 2026
+98
−92
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e8c57cf
[Attention][TurboQuant] Share decode buffers across layers
bhoomit 9f9c53c
[Attention][Refactor] Use WorkspaceManager for TQ decode buffers, rem…
bhoomit 95621a1
[Attention][Cleanup] Drop test_tq_shared_buffers.py
bhoomit 5f994a9
perf(attn): Share dequant buffers, eliminate float16_copy
bhoomit 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
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
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
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.
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.
While removing
torch.catis a great improvement, allocatingk_fullandv_fullviatorch.emptyinside the request loop still triggers an 'allocation storm' and increases peak memory usage, especially at long context (e.g., 1M tokens).Additionally, the explicit
.to(qdtype)on lines 783 and 785 creates redundant temporary tensors. Ifqdtypeisbfloat16(common for many models), this allocates an extra 8GB per tensor at 1M context before copying into the destination.Consider using
current_workspace_manager().get_simultaneous()to allocatek_fullandv_fullfrom the shared pool, and use.copy_()for in-place casting to avoid temporary allocations.