-
Notifications
You must be signed in to change notification settings - Fork 264
[DO NOT MERGE][Test] DSV4 FP4 B300 SGLang AgentX DEP8 c512 on nightly (HiCache + MegaMoE FP4-act) #2680
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
Open
yhyang201
wants to merge
2
commits into
main
Choose a base branch
from
yhyang201/dsv4-b300-sglang-c512-nightly-test
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−4
Open
[DO NOT MERGE][Test] DSV4 FP4 B300 SGLang AgentX DEP8 c512 on nightly (HiCache + MegaMoE FP4-act) #2680
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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.
🔴 The new
CONC>=512branch indsv4_fp4_b300_sglang_mtp.sh(megamoe A2A backend,SGLANG_OPT_DEEPGEMM_MEGA_MOE_*env vars,--enable-deepseek-v4-fp4-indexer, mem-fraction 0.85, chunked-prefill 131072) is gated only onDP_ATTENTIONandCONC, with no check on image or config key. The existing production configdsv4-fp4-b300-sglang-agentic-hicache-mtp(pinned tov0.5.17-cu130) already has a DEP8 arm withdp-attn: trueandconc-listincluding 512, so it will also hit this nightly-only branch — contradicting the PR description's claim that "Existing entries untouched" and risking a startup failure or silently altered baseline on that production c512 point.Extended reasoning...
The bug:
benchmarks/single_node/agentic/dsv4_fp4_b300_sglang_mtp.shis the single shared launcher for both the pre-existingdsv4-fp4-b300-sglang-agentic-hicache-mtpconfig (imagelmsysorg/sglang:v0.5.17-cu130) and the newdsv4-fp4-b300-sglang-agentic-hicache-mtp-nightlyconfig (imagelmsysorg/sglang:nightly-dev-cu13-20260818-c0b6474b) added in this PR. Both keys resolve to this script because they sharemodel-prefix: dsv4,precision: fp4,runner: b300-nv,framework: sglang, and theagentic-codingscenario.Code path: In
configs/nvidia-master.yaml, the existingdsv4-fp4-b300-sglang-agentic-hicache-mtpconfig's last arm is{ tp: 8, ep: 8, dp-attn: true, kv-offloading: none, spec-decoding: mtp, conc-list: [52, 72, 100, 128, 144, 196, 512], router: {...} }— notedp-attn: trueand512already in itsconc-list. When this arm's c512 point runs, the script receivesDP_ATTENTION=trueandCONC=512. The new branch added at lines 129-146 (if [ "$CONC" -ge 512 ]) and the indexer flag at lines 157-159 (if [ "$DP_ATTENTION" = "true" ] && [ "$CONC" -ge 512 ]) check nothing about which config or image is invoking the script — they fire purely on the env varsDP_ATTENTION/CONCset by whatever caller runs them.Why nothing prevents this: The script has no notion of "which config key called me" or "which image am I running under" — it's purely parameterized by env vars (
TP,CONC,DP_ATTENTION,KV_OFFLOADING, etc.), and both the old and new config's DEP8/c512 arms produce the identicalDP_ATTENTION=true, CONC=512combination. There's no image-version check, no dedicated flag (e.g. checkingKV_OFFLOADING=dram— which does differ between the two configs, since the existing arm useskv-offloading: nonewhile the nightly arm useskv-offloading: dram), so the gate is broader than intended.Impact: Before this PR, the existing v0.5.17 c512 point ran with
MEM_FRACTION_STATIC=0.94,CHUNKED_PREFILL_SIZE=16384, no--moe-a2a-backend megamoe, and no--enable-deepseek-v4-fp4-indexer. After this PR merges, that same production entry's c512 point will additionally receive--moe-a2a-backend megamoe, threeSGLANG_OPT_DEEPGEMM_MEGA_MOE_*env vars,--enable-deepseek-v4-fp4-indexer,MEM_FRACTION_STATICdropped to 0.85, andCHUNKED_PREFILL_SIZEraised to 131072. The PR description itself frames megamoe/the fp4-indexer flag as nightly-only capabilities being validated on the new nightly image — on the pinnedv0.5.17-cu130image these flags may not be recognized bysglang.launch_server's argparse, causing an immediate startup failure, or if they happen to exist, they'd silently change the production baseline's launch recipe. Either way this directly contradicts the PR description's explicit claim "Existing entries untouched."Step-by-step proof:
configs/nvidia-master.yaml(pre-existing, line ~1174):dsv4-fp4-b300-sglang-agentic-hicache-mtp→ arm{ tp: 8, ep: 8, dp-attn: true, kv-offloading: none, spec-decoding: mtp, conc-list: [..., 512] }.DP_ATTENTION=true,CONC=512,KV_OFFLOADING=none.if [ "$DP_ATTENTION" = "true" ]; then→ true, enters DP-attn branch, setsMEM_FRACTION_STATIC=0.95.if [ "$CONC" -ge 512 ]; then→ true (512 >= 512) — this is new logic added by this PR with no image/config check.PARALLEL_ARGS+=(--moe-a2a-backend megamoe), exports the threeSGLANG_OPT_DEEPGEMM_MEGA_MOE_*vars, setsMEM_FRACTION_STATIC=0.85,CHUNKED_PREFILL_SIZE=131072.if [ "$DP_ATTENTION" = "true" ] && [ "$CONC" -ge 512 ]; then MODEL_ARGS+=(--enable-deepseek-v4-fp4-indexer); fi→ true, adds the indexer flag.sglang.launch_serveris invoked on imagev0.5.17-cu130with these nightly-only flags/env vars it was never validated against — the production c512 point's recipe has changed from what it was before this PR, or fails to launch outright.Fix: Scope the new branch to the nightly config specifically — e.g., gate on
KV_OFFLOADING = "dram"(which does differ: the existing arm useskv-offloading: none, the nightly arm useskv-offloading: dram) or introduce an explicit env var/flag set only by the new nightly config key, rather than keying purely offCONC -ge 512.