[ROCm][DSv4] Enable confidence-based adaptive scheduler for DSpark - #56942
Closed
larryli2-amd wants to merge 3 commits into
Closed
larryli2-amd wants to merge 3 commits into
larryli2-amd wants to merge 3 commits into
Conversation
ve scheduler for DSpark Inherits vllm-project#52362. Signed-off-by: larryli2-amd <larryli2@amd.com>
larryli2-amd
requested review from
AndreasKaratzas,
dllehr-amd,
hongxiayang,
pavanimajety,
tjtanaa and
zyongye
as code owners
September 15, 2026 04:03
Contributor
Author
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.
Inherits #52362
This work inherits and rebases the ROCm DSpark adaptive-verification implementation from #52362. It is not an independent implementation of the feature.
This branch should only be submitted after explicit coordination with the author of #52362, or after that pull request is closed. If submitted as a replacement, it supersedes #52362 and preserves its original design and attribution.
Summary
Enable confidence-scheduled DSpark adaptive verification for DeepSeek-V4 on ROCm.
The change:
compute_confidence()with an explicitRuntimeError;Source Revision
larryli2-amd:enable_adaptive-dspark-rocm945abd627010c926cbf288f4b374e8b63d7443bfbbbd0a02c9d1bec965ee818af29a1319baefa69cFocused Validation
Result:
10 passed.The tests cover confidence-head mapping/loading/fail-closed behavior, the explicit missing-head error, ROCm adaptive CUDA-graph support, flattened query-length selection, the single-request uniform path, and stable buffer replay under changed allocations.
Changed-file lint and formatting checks also passed.
Serving Smoke Validation
A live
adaptive_k7ROCm serving smoke test completed successfully:/healthreturned HTTP 200;Application startup completewas observed;HSA_STATUS_ERROR_MEMORY_FAULT, worker death, queue hang, or traceback was observed;use_flattening=True;Observed speculative-decoding counters during the smoke request:
This demonstrates that the DSpark speculative path executed. It is not a throughput, latency, quality, or adaptive-vs-fixed performance measurement.
Reproduction Environment
Hardware
Model
deepseek-ai/DeepSeek-V4-Flash-DSpark/models/DeepSeek-V4-Flash-DSparkDeepseekV4ForCausalLMconfig.jsonSHA256:6c8f3d2d3b48707541b88f32f22ef3f0f8a6b57d8523281e2b8d3cdb0ae9a023model.safetensors.index.jsonSHA256:98efab455cf08dfbbbaaba6f570e1bf10bf927d2b4c3c453a59c2f6f0e3be92bContainer Provenance
The performance validation used a locally derived, pinned image:
The exact image tag is a locally derived artifact rather than a public registry image. A byte-identical reproduction requires access to that image or reconstruction from the pinned base digest and the exact AITer wheel above.
Serving Configuration
Throughput Methodology
The benchmark used a frozen 880-request SPEED-Bench Throughput-1K request set:
Each cell used an independent cold server boot. Warmup was:
A result is valid only when client and server generated-token counts match, no preemptions occur, and no GPU fault is observed.
Resutls
The results are expected: Compared with the non-adaptive scheduler, DSpark with the confidence-based adaptive scheduler delivers comparable performance at low concurrency and significant speedup at high concurrency.