fix(pd): account for KV transfer pages in mem_fraction - #1495
Open
sufubao wants to merge 3 commits into
Open
Conversation
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.
Summary
Motivation
The PD transfer process allocates its GPU page buffer after model initialization and KV-cache profiling, so mem_fraction could consume that space before the transfer process starts. With Qwen3.5-27B, 16 pages, page size 4096, 17 full-attention KV layers, 4 global KV heads, head dimension 256, and BF16, the unprofiled allocation is 4.25 GiB per GPU.
This change subtracts the exact allocation size from the automatic KV-cache budget. Normal and PD-master modes are unchanged, and an explicit max_total_token_num continues to bypass automatic profiling.
Validation
Validation note
ACP GPU end-to-end validation was not run from the local macOS development environment.