Repository navigation
[DSv4.1] Enable DeepGEMM sparse prefill under CP - #40613
Open
Silas-Zeng wants to merge 3 commits into
Open
Silas-Zeng wants to merge 3 commits into
Silas-Zeng wants to merge 3 commits into
Conversation
Silas-Zeng
force-pushed
the
feat/dsv41-cp-sparse-prefill
branch
from
September 22, 2026 16:33
69244f5 to
4b40020
Compare
Silas-Zeng
marked this pull request as ready for review
September 22, 2026 16:39
Silas-Zeng
requested review from
Fridge003,
HaiShaw,
Qiaolin-Yu,
hebiao064,
ispobock and
merrymercy
as code owners
September 22, 2026 16:39
Silas-Zeng
force-pushed
the
feat/dsv41-cp-sparse-prefill
branch
from
September 22, 2026 16:50
4b40020 to
d543204
Compare
Silas-Zeng
force-pushed
the
feat/dsv41-cp-sparse-prefill
branch
from
September 22, 2026 18:11
d543204 to
d7258b3
Compare
This branch has not been deployed
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.
Problem
This addresses item 3 of #40574 and follows #40352.
CP prefill currently scores every consumer index layer densely. The source publishes 2,048 blocks of 8 compressed positions per query row, but CP local rows do not line up with the shared page table, so consumers fall back to dense scoring. This change scores only the candidate blocks published by the indexer.
Change
req_to_tokenand reordered byapply_cp_reindex, including compact tails.Validation
The GPU validation used 2x NVIDIA B200 (SM100), driver 580.126.09, Ubuntu 24.04, Python 3.12.3, CUDA 13.0, PyTorch 2.13.0+cu130, and
sgl-deep-gemm0.2.0._publish_prefillimplementation and passes with this change.Existing score-floor thresholds were unchanged. The seed-17 failures match the dependency baseline at compression ratios 1 and 2. BF16 top-k, physical-slot, and cache checks pass in all eight scenarios. The rebase changed the in-tree test harness; CI should rerun the GPU suite on the final head.
Benchmark
Single-GPU component benchmark with random inputs and a simulated CP2 rank-0 layout. Five warmups and 30 synchronized timed runs per arm, using the same inputs and resident page tables/output buffers while alternating the dense and sparse arms. Peak memory is measured above the shared resident baseline:
At 4K context, sparse scoring uses about 23% more temporary allocated memory.
CI States
Latest PR Test (Base): ❌ Run #35767171561
Latest PR Test (Extra): ❌ Run #35767170888
Latest PR Test (AMD ROCm 10): ❌ Run #35767171044