Skip to content

[WIP] Test DeepSeek-V4 GB300 Dynamo AgentX recipes / 测试 DeepSeek-V4 GB300 Dynamo AgentX 配置 - #2302

Open
ivanium wants to merge 3 commits into
mainfrom
agentx/dsv4-gb200-pd-rev
Open

[WIP] Test DeepSeek-V4 GB300 Dynamo AgentX recipes / 测试 DeepSeek-V4 GB300 Dynamo AgentX 配置#2302
ivanium wants to merge 3 commits into
mainfrom
agentx/dsv4-gb200-pd-rev

Conversation

@ivanium

@ivanium ivanium commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • validate three DeepSeek-V4-Pro NVFP4 GB300 Dynamo-vLLM AgentX MTP prefill/decode topologies at concurrency 256, 512, and 768
  • increase the embedded Mooncake segment to 180 GB per GPU and exclude compute nodes with unhealthy shared-filesystem mounts
  • fix the failed sweep by validating existing squash cache entries before taking the NFS lock and by making AIPerf honor the configured 60-second synthesized-warmup concurrency ramp
  • sync the branch with the latest main and re-append this PR's changelog entry at the tail

AIPerf dependency fix: SemiAnalysisAI/aiperf#38

Validation

  • bash -n runners/launch_gb300-nv.sh benchmarks/benchmark_lib.sh
  • 224 matrix-logic tests passed
  • 31 changelog and GB200/GB300 launcher contract tests passed
  • 96 focused AIPerf converter, timing, and generated-schema tests passed
  • AIPerf pre-commit suite passed

中文说明

  • 验证三组 DeepSeek-V4-Pro NVFP4 GB300 Dynamo-vLLM AgentX MTP 预填充/解码拓扑,并发分别为 256、512 和 768
  • 将每张 GPU 的 Mooncake 内嵌共享内存段增至 180 GB,并排除共享文件系统挂载异常的计算节点
  • 修复本轮扫描失败:命中已有 Squash 缓存时先进行无锁校验,避免触发不受支持的 NFS flock;同时让 AIPerf 的自动生成预热阶段真正应用已配置的 60 秒并发爬升,防止快照预热请求压垮 Dynamo 预填充入口
  • 将分支同步到最新 main,并按追加式变更日志规则将本 PR 条目重新放到文件末尾

AIPerf 依赖修复:SemiAnalysisAI/aiperf#38

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! Please reach out to respective companies' CODEOWNER to fill in the latest PR_REVIEW_CHECKLIST.md before pinging core maintainer on Slack for review. In order for the signoff PR check bot to trigger, you must follow the PR_REVIEW_CHECKLIST.md template correctly, including the phrase As a PR reviewer and CODEOWNER, I have reviewed this and have.

For PR verification, add the full-sweep-fail-fast label (strongly recommended) to this PR — the benchmark sweep only runs on labeled PRs. Use full-sweep-enabled only if you need matrix jobs to keep running past a failure.

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. See GitHub's docs on re-running failed jobs


感谢你的贡献!请联系相应公司的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,然后再在 Slack 上联系核心维护者进行审阅。为了触发 signoff PR 检查机器人,你必须正确遵循 PR_REVIEW_CHECKLIST.md 模板,包括保留英文语句 As a PR reviewer and CODEOWNER, I have reviewed this and have

如需进行 PR 验证,请为此 PR 添加 full-sweep-fail-fast 标签(强烈推荐)— 基准测试 sweep 仅在带有标签的 PR 上运行。仅当需要矩阵任务在失败后继续运行时才使用 full-sweep-enabled

PR 作者有责任确保合并后所有 GitHub Action 任务完全通过。 很多时候失败只是偶发抖动(flake),重新运行失败的任务即可解决。参见 GitHub 关于重新运行失败任务的文档

@ivanium
ivanium marked this pull request as ready for review July 22, 2026 20:47
@ivanium
ivanium requested a review from a team July 22, 2026 20:47
@claude

claude Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Claude finished @ivanium's task in 6m 24s —— View job


PR Review

  • Gather context and read the full diff
  • Review new recipes, master config, changelog, and launcher changes
  • Check CI status and root-cause the failing check-changelog job
  • Post inline review comments

Summary

Found 1 blocking issue and 2 warnings (details in inline comments):

  • 🔴 CI is hard-blocked: the check-changelog job fails because the branch is stale — main gained a perf-changelog.yaml entry (PR [AMD][dsv4] Fix 2P1D eval 503s/straggler tail, retune disagg concurrency sweep #2293) after this branch forked, and the validator's two-dot diff against origin/main sees it as a forbidden deletion, which skips the entire benchmark sweep. Merge latest main (keeping the new entry at the end of the file) and re-trigger.
  • 🟡 The IS_AGENTIC checkpoint switch (DeepSeek-V4-Pro-NVFP4/DeepSeek-V4-Pro/) also applies to the two existing GB200 agentic configs (...-agentic-2p1d-dep8-dep8, ...-agentic-3p2d-tep8-tp8), silently changing their model under unchanged config keys, undocumented in the changelog.
  • 🟡 The srt-slurm switch from a pinned fork commit to unpinned NVIDIA/srt-slurm:main also affects those existing recipes (which still pin dynamo.wheel, a feature the removed comment described as fork-only) and reintroduces reproducibility drift; please pin a validated commit and confirm the existing 2p1d/3p2d recipes still run on upstream.

The rest looks good: new recipe YAMLs are well-documented, the num-worker: 0 aggregate-decode accounting matches the GB300 precedent, the perf-changelog entry is correctly appended at the end, the container image is a public Docker Hub reference, and the benchmark_lib.sh opt-out is backward-compatible (default unchanged).

Comment thread perf-changelog.yaml
Comment thread runners/launch_gb200-nv.sh Outdated
Comment thread runners/launch_gb200-nv.sh Outdated
@ivanium ivanium changed the title Add DeepSeek-V4 GB200 Dynamo AgentX recipes / 新增 DeepSeek-V4 GB200 Dynamo AgentX 配方 Test DeepSeek-V4 GB200 Dynamo AgentX recipes / 测试 DeepSeek-V4 GB200 Dynamo AgentX 配方 Jul 22, 2026

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds new multi-node GB200 AgentX recipes and modifies shared launcher/routing logic, including a change to configs/nvidia-master.yaml (a CODEOWNER-protected file), so it's worth a human look before merging.

What was reviewed: the two new srt-slurm recipe YAMLs (aggregate TP8 and disaggregated 3P1D DEP8/DEP16), the launch_gb200-nv.sh model-path routing and srt-slurm source switch for agentic runs, the benchmark_lib.sh aiperf conv-aware-routing opt-out, and the new nvidia-master.yaml/perf-changelog.yaml entries.

Extended reasoning...

Overview

The PR adds two new DeepSeek-V4 GB200 Dynamo AgentX recipes (aggregate TP8 and disaggregated 3P1D DEP8/DEP16), registers them in configs/nvidia-master.yaml and perf-changelog.yaml, and modifies two shared scripts: benchmarks/benchmark_lib.sh (adds an opt-out env var for aiperf's dynamo conv-aware-routing flag) and runners/launch_gb200-nv.sh (switches the agentic srt-slurm clone from a pinned fork to NVIDIA/srt-slurm:main, and branches MODEL_PATH resolution for DSV4 FP4 based on IS_AGENTIC).

Security risks

No security-sensitive surface — this is internal benchmark/CI infrastructure (Slurm job launching, recipe YAML, shell env plumbing) with no auth, crypto, or externally-reachable inputs. The git clone URLs and container images are pinned to specific orgs/tags rather than user-controlled input.

Level of scrutiny

Higher than typical for this repo: the diff touches shared launcher logic (launch_gb200-nv.sh) and the aiperf routing default in benchmark_lib.sh, both of which affect existing non-agentic GB200 runs in addition to the new recipes. It also modifies configs/nvidia-master.yaml, which is CODEOWNER-protected (@ankur-singh @kedarpotdar-nv @InferenceX/core). Combined with the size and multi-file nature of the change (new multi-node recipes with many tuned env vars, a repo-source switch for the agentic srt-slurm path, and conditional model-path logic), this warrants a human pass rather than auto-approval.

Other factors

The bug-hunting system found no bugs, and several candidate issues (leftover NCCL symm-mem env var, an odd tokenizer string, --no-preflight usage, combining kv-cache-memory with gpu-memory-utilization) were raised and ruled out as not real bugs. The PR description/comments show no CODEOWNER sign-off yet per the standard recipe-PR checklist, which is itself a signal that human review is expected before merge.

ivanium added a commit that referenced this pull request Jul 22, 2026
Merge current upstream/main and rebuild the append-only performance changelog with PR #2302 at the tail.

中文:同步上游 main。合并当前 upstream/main,并基于最新文件重新在性能变更日志末尾追加 PR #2302 条目。
@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from baca859 to 99a28ab Compare July 23, 2026 03:17
@github-actions

Copy link
Copy Markdown
Contributor

@ivanium ivanium changed the title Test DeepSeek-V4 GB200 Dynamo AgentX recipes / 测试 DeepSeek-V4 GB200 Dynamo AgentX 配方 [WIP] Test DeepSeek-V4 GB300 Dynamo AgentX recipes Jul 25, 2026
ivanium added a commit that referenced this pull request Jul 25, 2026
Add four GB300 MTP3 AgentX topologies using the bedf79e image: aggregate TP8, 1P/1D DEP4/DEP8, 1P/1D DEP8/DEP8, and 2P/1D DEP8/DEP16. Follow PR #2157's aggregate/disaggregated organization, PR #2269's CI rack networking, and PR #2302's upstream srt-slurm per-node launch path with automatic hybrid load balancing. Configure each disaggregated decode-side MooncakeStore connector as a synchronous KV consumer with lookup disabled while preserving the prefill-side configuration.

中文:新增四个使用 bedf79e 镜像的 GB300 MTP3 AgentX 拓扑:聚合式 TP8、1P/1D DEP4/DEP8、1P/1D DEP8/DEP8 和 2P/1D DEP8/DEP16。配置组织遵循 PR #2157 的聚合式/分离式结构,网络设置对齐 PR #2269 的 CI 机架环境,并依据 PR #2302 使用上游 srt-slurm 的单节点单进程启动模式及其自动启用的混合负载均衡。仅将各分离式配置解码侧的 MooncakeStore 连接器设为同步 KV 消费端并关闭查找功能,同时保留预填充侧原有配置。
@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from 99a28ab to 985c29e Compare July 25, 2026 10:28
ivanium added a commit that referenced this pull request Jul 25, 2026
Add four GB300 MTP3 AgentX topologies using the bedf79e image: aggregate TP8, 1P/1D DEP4/DEP8, 1P/1D DEP8/DEP8, and 2P/1D DEP8/DEP16. Follow PR #2157's aggregate/disaggregated organization, PR #2269's CI rack networking, and PR #2302's upstream srt-slurm per-node launch path with automatic hybrid load balancing. Align all disaggregated recipes on Dynamo 1.3.0.dev20260720, preserve prefill-only connector prefetch and breakable CUDA graph settings, and configure decode-side MooncakeStore as a synchronous KV consumer with lookup disabled.

中文:新增四个使用 bedf79e 镜像的 GB300 MTP3 AgentX 拓扑:聚合式 TP8、1P/1D DEP4/DEP8、1P/1D DEP8/DEP8 和 2P/1D DEP8/DEP16。配置组织遵循 PR #2157 的聚合式/分离式结构,网络设置对齐 PR #2269 的 CI 机架环境,并依据 PR #2302 使用上游 srt-slurm 的单节点单进程启动模式及其自动启用的混合负载均衡。所有分离式配置统一使用 Dynamo 1.3.0.dev20260720,连接器预取和可中断 CUDA Graph 设置仅保留在预填充侧;解码侧 MooncakeStore 设为同步 KV 消费端并关闭查找功能。
@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from 985c29e to dfc774f Compare July 25, 2026 10:37
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

ivanium added a commit that referenced this pull request Jul 26, 2026
Add four GB300 MTP3 AgentX topologies using the bedf79e image: aggregate TP8, 1P/1D DEP4/DEP8, 1P/1D DEP8/DEP8, and 2P/1D DEP8/DEP16. Follow PR #2157's aggregate/disaggregated organization, PR #2269's CI rack networking, and PR #2302's upstream srt-slurm per-node launch path with automatic hybrid load balancing. Align all disaggregated recipes on Dynamo 1.3.0.dev20260720, preserve prefill-only connector prefetch and breakable CUDA graph settings, and configure decode-side MooncakeStore as a synchronous KV consumer with lookup disabled.

中文:新增四个使用 bedf79e 镜像的 GB300 MTP3 AgentX 拓扑:聚合式 TP8、1P/1D DEP4/DEP8、1P/1D DEP8/DEP8 和 2P/1D DEP8/DEP16。配置组织遵循 PR #2157 的聚合式/分离式结构,网络设置对齐 PR #2269 的 CI 机架环境,并依据 PR #2302 使用上游 srt-slurm 的单节点单进程启动模式及其自动启用的混合负载均衡。所有分离式配置统一使用 Dynamo 1.3.0.dev20260720,连接器预取和可中断 CUDA Graph 设置仅保留在预填充侧;解码侧 MooncakeStore 设为同步 KV 消费端并关闭查找功能。
@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from 8a83d53 to 64f87af Compare July 26, 2026 19:34
ivanium added a commit that referenced this pull request Jul 26, 2026
Add four GB300 MTP3 AgentX topologies using the bedf79e image: aggregate TP8, 1P/1D DEP4/DEP8, 1P/1D DEP8/DEP8, and 2P/1D DEP8/DEP16. Follow PR #2157's aggregate/disaggregated organization, PR #2269's CI rack networking, and PR #2302's upstream srt-slurm per-node launch path with automatic hybrid load balancing. Align all disaggregated recipes on Dynamo 1.3.0.dev20260720, preserve prefill-only connector prefetch and breakable CUDA graph settings, and configure decode-side MooncakeStore as a synchronous KV consumer with lookup disabled.

中文:新增四个使用 bedf79e 镜像的 GB300 MTP3 AgentX 拓扑:聚合式 TP8、1P/1D DEP4/DEP8、1P/1D DEP8/DEP8 和 2P/1D DEP8/DEP16。配置组织遵循 PR #2157 的聚合式/分离式结构,网络设置对齐 PR #2269 的 CI 机架环境,并依据 PR #2302 使用上游 srt-slurm 的单节点单进程启动模式及其自动启用的混合负载均衡。所有分离式配置统一使用 Dynamo 1.3.0.dev20260720,连接器预取和可中断 CUDA Graph 设置仅保留在预填充侧;解码侧 MooncakeStore 设为同步 KV 消费端并关闭查找功能。
@github-actions

Copy link
Copy Markdown
Contributor

ivanium added a commit that referenced this pull request Jul 27, 2026
Add three GB300 MTP3 AgentX topologies using the bedf79e image: aggregate TP8, 1P/1D DEP4/DEP8, and 1P/1D DEP8/DEP8. Follow PR #2157's aggregate/disaggregated organization, PR #2269's CI rack networking, and PR #2302's upstream srt-slurm per-node launch path with automatic hybrid load balancing. Align both disaggregated recipes on Dynamo 1.3.0.dev20260720, preserve prefill-only connector prefetch and breakable CUDA graph settings, and configure decode-side MooncakeStore as a synchronous KV consumer with lookup disabled.

中文:新增三个使用 bedf79e 镜像的 GB300 MTP3 AgentX 拓扑:聚合式 TP8、1P/1D DEP4/DEP8 和 1P/1D DEP8/DEP8。配置组织遵循 PR #2157 的聚合式/分离式结构,网络设置对齐 PR #2269 的 CI 机架环境,并依据 PR #2302 使用上游 srt-slurm 的单节点单进程启动模式及其自动启用的混合负载均衡。两个分离式配置统一使用 Dynamo 1.3.0.dev20260720,连接器预取和可中断 CUDA Graph 设置仅保留在预填充侧;解码侧 MooncakeStore 设为同步 KV 消费端并关闭查找功能。
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@ivanium

ivanium commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator Author

/stage-results 31302825977

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

@ivanium staged run 31302825977: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-09~r31302825977

This run remains available across future /stage-results requests. Staging the same run ID again updates its staged data. Staging workflow

@ivanium 已将运行 31302825977 发布到预发布环境:https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-09~r31302825977

后续的 /stage-results 请求不会移除此运行;再次发布相同的运行 ID 会更新其预发布数据。预发布工作流

@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch 2 times, most recently from 6a190ec to 5794386 Compare August 9, 2026 22:30
@github-actions

Copy link
Copy Markdown
Contributor

ivanium added a commit that referenced this pull request Aug 10, 2026
Add a validated runner-node scheduling override that preserves the cluster hardware identity. Pin PR #2302 aggregate jobs to gb300-nv_0 and P/D jobs to gb300-nv_1 while gb300-nv_2 is repaired.\n\n中文:新增经过校验的 runner-node 调度覆盖字段,同时保留集群硬件标识。在 gb300-nv_2 修复期间,将 PR #2302 的聚合任务固定到 gb300-nv_0,并将预填充/解码分离任务固定到 gb300-nv_1。
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch 3 times, most recently from 2721733 to 44721d9 Compare August 10, 2026 22:55
@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from 44721d9 to c9f35d6 Compare August 11, 2026 07:48
@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch 2 times, most recently from 5b14616 to e74b093 Compare August 12, 2026 09:04
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

新增与 TensorRT-LLM c736 点相同的 2P1D DEP8/DEP32 拓扑。vLLM 使用合成接受长度 2.97,以对应 TensorRT-LLM 的 1.97 记法。
新增 GB300 vLLM AgentX 1P1D DEP8/DEP32 c388 点,并保留现有 c736 配置与结果历史。
新增 vLLM GB300 c4、c12 和 c24 低延迟配置,并从当前生成的扫描矩阵中移除 c736 和 c388。
@ivanium
ivanium force-pushed the agentx/dsv4-gb200-pd-rev branch from 3332492 to ecc6dc6 Compare August 18, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agentx AgentX benchmarks, recipes, and infrastructure full-sweep-fail-fast

Projects

Development

Successfully merging this pull request may close these issues.

2 participants