Skip to content

perf(gb300): Add more AgentX vLLM MTP aggregate and P/D recipes / 增加更多 GB300 AgentX vLLM MTP 聚合与 P/D 配方 - #2665

Merged
cquil11 merged 6 commits into
mainfrom
agent/update-gb300-agentx-vllm-mtp-pd
Aug 25, 2026
Merged

perf(gb300): Add more AgentX vLLM MTP aggregate and P/D recipes / 增加更多 GB300 AgentX vLLM MTP 聚合与 P/D 配方#2665
cquil11 merged 6 commits into
mainfrom
agent/update-gb300-agentx-vllm-mtp-pd

Conversation

@ivanium

@ivanium ivanium commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Summary / 摘要

English

  • Add a few TP4 agg and DEP32 disagg recipes.

中文

  • 增加一些额外的 TP4 agg 和 DEP32 disagg 配方。

Validation / 验证

  • 19 generated configs, 232 matrix tests, YAML/topology/launcher/diff checks passed. / 生成 19 个配置,232 项矩阵测试及 YAML、拓扑、启动器和差异检查均通过。

Note

Low Risk
Benchmark and Slurm recipe YAML plus master matrix wiring only; no runtime service or library code changes.

Overview
Adds four GB300 DeepSeek-V4 AgentX disaggregated MTP benchmark recipes and wires them into nvidia-master.yaml under dsv4-fp4-gb300-dynamo-vllm-agentic-mtp-disagg, with a matching perf-changelog.yaml entry.

Three 1P1D recipes scale proven DEP8/DEP32-style points down to DEP4 prefill + DEP16 decode at concurrency 128 and 256 (Mooncake + NIXL KV, decode disables Mooncake prefix lookup). A fourth 1P1D point keeps DEP8 + DEP16 for c512.

A separate 1P4D recipe targets high interactivity at c4: one DEP4 prefill feeds four TP8 decode workers via NIXL only, Dynamo KV router, prefill KV events, FlashInfer allreduce on multi-node decode, and benchmark client colocated on first decode.

Throughput-oriented matrix entries use synthetic MTP acceptance at launch; the c4 1P4D recipe is positioned for eval runs with real MTP output.

Reviewed by Cursor Bugbot for commit ace786e. Bugbot is set up for automated code reviews on this repo. Configure here.

@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 force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from 185f2e3 to ad2c1a8 Compare August 19, 2026 02:02
@ivanium ivanium changed the title perf(gb300): refresh AgentX vLLM MTP P/D recipes / 刷新 GB300 AgentX vLLM MTP P/D 配方 perf(gb300): refresh AgentX vLLM MTP aggregate and P/D recipes / 刷新 GB300 AgentX vLLM MTP 聚合与 P/D 配方 Aug 19, 2026
@ivanium
ivanium marked this pull request as ready for review August 19, 2026 06:29
@ivanium
ivanium requested a review from a team August 19, 2026 06:29
@ivanium
ivanium marked this pull request as draft August 19, 2026 06:42
@ivanium
ivanium marked this pull request as ready for review August 19, 2026 06:46

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

Beyond the inline finding on the checked-in synthetic MTP config, I also checked the new 1P3D GB300 recipe (disagg-gb300-1p3d-dep4-tp8-c3-mtp-agentic.yaml) for missing multi-node NCCL/UCX env vars on the cross-node TP8 decode workers — this was examined and ruled out.

Extended reasoning...

Bugs were found in this run and are already posted as inline comments; this note only records an additional item that was examined and ruled out, not a full re-review.

@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from be4e8ef to 023bf49 Compare August 19, 2026 06:57
@ivanium ivanium added agentx AgentX benchmarks, recipes, and infrastructure full-sweep-enabled labels Aug 19, 2026
@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

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from 2f96942 to 7f1d3ae Compare August 22, 2026 23:53
@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from 7f1d3ae to 1ef7058 Compare August 22, 2026 23:59
@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch 2 times, most recently from 55e4a1e to ad2e946 Compare August 23, 2026 00:06
@github-actions

Copy link
Copy Markdown
Contributor

@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from ad2e946 to 9dce474 Compare August 24, 2026 07:31
@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

仅追加已验证的 GB300 AgentX P/D 点:DEP8/DEP16 c512,以及 DEP4 配合四个 TP8 解码 worker 的 c4。保留所有现有点和配方不变,并将性能变更记录标记为 append-only。
追加已验证的 GB300 AgentX DEP4 预填充、DEP16 解码并发 128 点位。
追加已验证的 GB300 AgentX DEP4 预填充、DEP16 解码并发 256 点位,并使用解码侧 8/32/32 限制。
将 PR #2665 的性能变更记录合并为一个简洁的 append-only 条目。
@ivanium
ivanium force-pushed the agent/update-gb300-agentx-vllm-mtp-pd branch from 9dce474 to 54d9faf Compare August 25, 2026 04:34
@github-actions

Copy link
Copy Markdown
Contributor

@cquil11

cquil11 commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

/stage-results 32809502132

@github-actions

github-actions Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

@cquil11 staged run 32809502132: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-08-25~r32809502132

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

@cquil11

cquil11 commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator

/reuse-sweep-run 32809502132

@cquil11
cquil11 merged commit c1f5be9 into main Aug 25, 2026
8 checks passed
@cquil11
cquil11 deleted the agent/update-gb300-agentx-vllm-mtp-pd branch August 25, 2026 20:21

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit ace786e. Configure here.

no-enable-flashinfer-autotune: true
block-size: 256
compilation-config: '{"cudagraph_mode":"FULL_DECODE_ONLY","mode":0}'
max-cudagraph-capture-size: 16

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Decode limits undersized after topology halved

High Severity

Halving DEP32 decode to DEP16 kept the original per-rank max-num-seqs, max-num-batched-tokens, and max-cudagraph-capture-size. Each decode rank now sees twice the load at the same concurrency, so c128 capacity is 64 sequences and c256 capacity is 128. The advertised points will queue half their in-flight requests and publish incorrect AgentX latency and throughput.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit ace786e. Configure here.

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-enabled

Projects

Development

Successfully merging this pull request may close these issues.

2 participants