feat(vllm): default DP launch to per-node hybrid LB - #272
Draft
alec-flowers wants to merge 2 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #272 +/- ##
=======================================
Coverage ? 67.40%
=======================================
Files ? 69
Lines ? 9108
Branches ? 0
=======================================
Hits ? 6139
Misses ? 2969
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
--data-parallel-size-local,--data-parallel-start-rank, DP address, and DP RPC port from the allocated topology.backend.legacy_dp_per_gpu: trueas a compatibility escape hatch for the previous one-process-per-DP-rank layout.This builds on and supersedes #90, but makes the per-node layout opinionated rather than adding per-role launch-mode tuning.
Registration and routing model
The Dynamo routing boundary is a registered
generateengine, not each internal vLLM DP rank.generateregistration per node/parent process. vLLM owns the node-local DP ranks below that registration and performs hybrid load balancing within the parent.generateregistration per vLLM DP process. vLLM is still launched with its global--data-parallel-rank, but Dynamo routes to each process as an independent engine.For DEP8 on two 4-GPU nodes, the default therefore creates two Dynamo engines. The two vLLM parents own global DP ranks 0-3 and 4-7 respectively. The Dynamo router does not see eight independently routable engines in this layout.
Configuration
Per-node hybrid is automatic when a vLLM role sets
data-parallel-size:The previous layout remains available as a deployment-wide compatibility switch:
Validation
Local
Real GB200 smoke tests
All tests used local DeepSeek-V4-Flash weights (not the Hugging Face cache), vLLM 0.25.0, and matching aarch64 nightly wheels:
ai-dynamo==1.3.0.dev20260718ai-dynamo-runtime==1.3.0.dev202607182424943COMPLETED 0:0; server healthy; smoke requests passed2424942_dp0-_dp3); NIXL compatibility passed on all decode ranksCOMPLETED 0:0; server healthy at 1P + 1D; smoke requests passed2424944legacy_dp_per_gpu: trueCOMPLETED 0:0; server healthy at 4P + 4D; smoke requests passedThe DEP8 logs also confirm
NCCL_SYMM_MEMwas selected for the DP and EP groups with the per-node parent layout.