Skip to content

Add DSV4 B200 disaggregated Dynamo SGLang MTP configuration / 新增 DSV4 B200 分离式 Dynamo SGLang MTP 配置 - #2252

Open
RohitNagraj wants to merge 9 commits into
mainfrom
dsv4-fp4-b200-dynamo-sglang-mtp
Open

Add DSV4 B200 disaggregated Dynamo SGLang MTP configuration / 新增 DSV4 B200 分离式 Dynamo SGLang MTP 配置#2252
RohitNagraj wants to merge 9 commits into
mainfrom
dsv4-fp4-b200-dynamo-sglang-mtp

Conversation

@RohitNagraj

@RohitNagraj RohitNagraj commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a DSV4 B200 disaggregated Dynamo SGLang MTP configuration for 8k/1k.
  • Add five checked-in srt-slurm recipes with EAGLE speculative decoding and chat-formatted benchmark inputs.
  • Use the staged DSV4 checkpoint's native quantization metadata and select the checkpoint-compatible MoE backend.
  • Use Mooncake's registered-memory pool with MNNVL transport selection instead of forcing a fixed HCA list.
  • Use an SGLang image containing DSV4 disaggregated MTP state-transfer support and pin the B200 launcher bootstrap to the verified uv 0.12.0 release.

Validation

  • Generated all configured throughput and evaluation sweep combinations successfully.
  • Validated launcher shell syntax, YAML parsing, recipe/config consistency, chat-template usage, and changelog ordering.
  • Passed the matrix-logic test suite.

中文说明

  • 新增 DSV4 在 B200 上的分离式 Dynamo SGLang MTP 8k/1k 配置。
  • 新增五个已检入的 srt-slurm recipe,启用 EAGLE 投机解码和聊天模板格式的基准测试输入。
  • 使用已暂存 DSV4 检查点原生的量化元数据,并选择与检查点兼容的 MoE 后端。
  • 使用 Mooncake 注册内存池和 MNNVL 传输选择,不再强制指定固定的 HCA 列表。
  • 使用包含 DSV4 分离式 MTP 状态传输支持的 SGLang 镜像,并将 B200 启动器引导程序固定到已校验的 uv 0.12.0 版本。

验证

  • 已成功生成全部吞吐量和评估扫描组合。
  • 已验证启动器 Shell 语法、YAML 解析、recipe 与配置的一致性、聊天模板使用情况以及变更日志顺序。
  • 已通过矩阵逻辑测试套件。

Add five recipe-backed 8k/1k MTP topologies and config-scoped B200 launcher handling.

中文:新增 DSV4 FP4 B200 分离式 Dynamo SGLang MTP 配置,加入五个由 recipe 驱动的 8k/1k MTP 拓扑,并将 B200 启动器处理限定到该配置。
@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 关于重新运行失败任务的文档

1 similar comment
@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 关于重新运行失败任务的文档

Record the public pull request URL in the final changelog entry.

中文:在性能变更日志的最后一个条目中记录公开拉取请求链接。

@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.

LGTM — straightforward addition of a new DSV4 NVFP4 B200 dynamo-sglang MTP disaggregated benchmark recipe, following existing patterns in this file.

Extended reasoning...

Overview

This PR adds a new benchmark recipe: DSV4 NVFP4 on B200 using dynamo-sglang with MTP (speculative decoding), disaggregated prefill/decode. It adds five new srt-slurm recipe YAML files (1p1d, 1p6d, and three mid-curve DP/EP topologies), a corresponding entry in configs/nvidia-master.yaml, a perf-changelog.yaml entry, and extends runners/launch_b200-dgxc.sh to support this new framework/model/precision/spec-decoding combination.

Security risks

None. All changes are benchmark configuration (YAML) and CI/runner shell script logic for launching internal SLURM benchmark jobs. No user input handling, auth, or credential logic is touched.

Level of scrutiny

Low-to-moderate. The five new YAML recipe files are pure data (env vars, sglang server flags, resource topology) with no control flow, so they carry no correctness risk beyond being internally consistent, which they are (prefill/decode node counts match the resources block, deepep configs are used consistently with enable-dp-attention, etc.). The one piece of actual logic is the runners/launch_b200-dgxc.sh change, which extends an existing if/elif chain to special-case the new dynamo-sglang plus dsv4 plus fp4 plus mtp combination (model path resolution, a new no-preflight flag, framework validation, and repo checkout/copy). This follows the same structural pattern already used for the adjacent dsr1/dynamo-sglang and dynamo-vllm/dsv4 branches, so it's a low-risk, mechanical extension rather than a new design.

Other factors

The bug-hunting pass found no issues, and my own read of the launcher script diff didn't surface any additional problems — the new PREFLIGHT_ARGS array is initialized unconditionally before use, and the updated multinode-framework-validation conditional correctly permits both the pre-existing dynamo-vllm path and the new dynamo-sglang plus mtp path for dsv4. This matches the shape of many prior benchmark-recipe-addition PRs in this repo that have been approved without human review.

@github-actions

Copy link
Copy Markdown
Contributor

Ankur-singh added a commit that referenced this pull request Jul 18, 2026
Merge current origin/main and resolve perf-changelog.yaml by retaining every main entry and re-appending PR #2252's entry at the end.\n\n中文:合并最新的 origin/main,并保留主分支的全部 perf-changelog.yaml 条目,将 PR #2252 的专属条目重新追加到文件末尾。
Merge current origin/main and resolve perf-changelog.yaml by retaining every main entry and re-appending PR #2252's entry at the end.

中文:合并最新的 origin/main,并保留主分支的全部 perf-changelog.yaml 条目,将 PR #2252 的专属条目重新追加到文件末尾。
@Ankur-singh
Ankur-singh force-pushed the dsv4-fp4-b200-dynamo-sglang-mtp branch from 2f1eeb4 to 8e6ce84 Compare July 18, 2026 18:57
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

5 similar comments
@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

@github-actions

Copy link
Copy Markdown
Contributor

中文:配置 DSV4 B200 SGLang 模型加载、RDMA 传输和固定版本的 uv 引导程序。
@github-actions

Copy link
Copy Markdown
Contributor

Remove synthetic checkpoint metadata and the loader-isolation override, select the checkpoint-compatible MoE backend, and update the staged checkpoint path while preserving the existing precision, topology, and transport settings.\n\n中文:移除合成的检查点元数据和仅用于隔离加载问题的设置,选择与检查点兼容的 MoE 后端,并更新已暂存的检查点路径,同时保留现有精度、拓扑和传输设置。
@RohitNagraj RohitNagraj changed the title Add DSV4 FP4 B200 disaggregated Dynamo SGLang MTP configuration / 新增 DSV4 FP4 B200 分离式 Dynamo SGLang MTP 配置 Add DSV4 B200 disaggregated Dynamo SGLang MTP configuration / 新增 DSV4 B200 分离式 Dynamo SGLang MTP 配置 Jul 31, 2026
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Restore the Mooncake registered-memory pool and MNNVL selection for all B200 MTP recipes, remove the forced HCA list, and use the SGLang image containing DSV4 disaggregated MTP state transfer.

中文:为所有 B200 MTP recipe 恢复 Mooncake 注册内存池和 MNNVL 传输选择,移除强制 HCA 列表,并使用包含 DSV4 分离式 MTP 状态传输支持的 SGLang 镜像。
@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Replace the unavailable SGLang image tag across the DSV4 B200 master configuration, five recipes, and changelog entry.

Synchronize the branch with current main and keep the PR changelog entry at the end.

中文:将 DSV4 B200 主配置、五个 recipe 和变更日志条目中的不可用 SGLang 镜像标签替换为已发布版本。同步当前 main,并将本 PR 的变更日志条目保留在文件末尾。
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

中文:将 DSV4 B200 SGLang 配置与最新 main 对齐,并保留已验证的镜像和启动修复。
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Replace the Mooncake MNNVL-specific memory pool settings with the B200 NIXL and UCX transport across all five disaggregated recipes. Refresh the branch from main and keep the PR changelog entry appended at the end.

中文:将五个分离式配方中的 Mooncake MNNVL 专用内存池配置替换为 B200 NIXL 和 UCX 传输。同步最新 main,并保持该 PR 的变更日志条目位于文件末尾。
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

2 similar comments
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants