Skip to content

[NV] Kimi K2.5 NVFP4 B200 disaggregated TRT-LLM (Dynamo) recipe#2249

Open
richardhuo-nv wants to merge 2 commits into
mainfrom
dynamo-trt-b200-kimik2.5-nvfp4
Open

[NV] Kimi K2.5 NVFP4 B200 disaggregated TRT-LLM (Dynamo) recipe#2249
richardhuo-nv wants to merge 2 commits into
mainfrom
dynamo-trt-b200-kimik2.5-nvfp4

Conversation

@richardhuo-nv

Copy link
Copy Markdown
Collaborator

[NV] kimik2.5-fp4-b200-dynamo-trt: Kimi K2.5 NVFP4 B200 disaggregated TRT-LLM (Dynamo) recipe

Summary

Adds a new multi-node benchmark config kimik2.5-fp4-b200-dynamo-trt — Kimi K2.5 NVFP4 on B200, disaggregated prefill/decode served via Dynamo + TensorRT-LLM. This is the B200 sibling of the existing kimik2.5-fp4-gb200-dynamo-trt entry, with topologies and engine configs sourced from the NVIDIA srt-slurm B200 recipes.

Scenario: ISL 8192 / OSL 1024, 11 STP (non-MTP) Pareto points.

Topologies

Config Prefill Decode Concurrency
1p4d-dep4-tep8 1×DEP4 4×TEP8 4, 24
1p5d-dep4-tep4 1×DEP4 5×TEP4 5, 30, 60, 115, 195
1p1d-dep4-dep8 1×DEP4 1×DEP8 308
2p1d-dep4-dep8 2×DEP4 1×DEP8 615
3p1d-dep4-dep8 3×DEP4 1×DEP8 1127
4p1d-dep4-dep8 4×DEP4 1×DEP8 2151
  • Container: nvcr.io/nvidia/tensorrt-llm/release:1.3.0rc21
  • Dynamo: installed from source (hash 4025cb6a8992d19fd19eead36065e08ea5301f35), nixl KV transfer, TCP request plane
  • Runner: b200-multinode (b200-dgxc-slurm)

Changes

  • benchmarks/multi_node/srt-slurm-recipes/trtllm/kimi-k2.5/disagg/trtllm_dynamo/b200-fp4/ — 11 flat recipe YAMLs copied from srt-slurm, with model.path/model.container rewritten to the cluster-resolved aliases (kimik2.5-fp4 / dynamo-trtllm)
  • configs/nvidia-master.yaml — new kimik2.5-fp4-b200-dynamo-trt entry (all 11 configs, each pointing at its local CONFIG_FILE)
  • runners/launch_b200-dgxc.sh — added a dynamo-trt + kimik2.5 + fp4 branch that clones srt-slurm and copies the local B200 recipes into recipes/trtllm/kimi-k25-nvfp4/b200-fp4/
  • perf-changelog.yaml — new changelog entry (selects this config for the sweep)

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

Comment thread perf-changelog.yaml Outdated
Comment thread perf-changelog.yaml Outdated
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

3 similar comments
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

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.

1 participant