Skip to content

Add Qwen3.5 H200 MTP config / 新增 Qwen3.5 H200 MTP 配置 - #2592

Open
hshrivastava-droid wants to merge 7 commits into
mainfrom
qwen3.5-fp8-h200-sglang-agentic-nv
Open

Add Qwen3.5 H200 MTP config / 新增 Qwen3.5 H200 MTP 配置#2592
hshrivastava-droid wants to merge 7 commits into
mainfrom
qwen3.5-fp8-h200-sglang-agentic-nv

Conversation

@hshrivastava-droid

Copy link
Copy Markdown
Collaborator

Description

  • Add an H200 FP8 SGLang AgentX MTP configuration for Qwen3.5 with DRAM HiCache.
  • Run TP8/EP1 at concurrency 2, 4, 8, 10, 12, 16, 20, and 24.
  • Pin agentic MTP throughput to golden acceptance length 3.39; evals retain real target-model verification.

中文说明

  • 为 Qwen3.5 新增 H200 FP8 SGLang AgentX MTP 配置,并启用 DRAM HiCache。
  • 使用 TP8/EP1,覆盖并发度 2、4、8、10、12、16、20 和 24。
  • AgentX MTP 吞吐量固定使用黄金接受长度 3.39;评测保留真实目标模型验证。

Related Issue

N/A

Type of Change

  • Bug fix
  • New feature
  • Configuration change
  • Documentation update
  • Other (please describe)

Checklist

  • I have tested my changes locally
  • I have updated documentation if necessary
  • For every change that can affect benchmark performance and every recipe addition or modification, I have appended a new entry to the physical end of perf-changelog.yaml and have not edited historical entries
  • Before merging via reuse, an authorized maintainer (OWNER/MEMBER/COLLABORATOR) has commented /reuse-sweep-run on this PR. Do this only once there is a final full sweep that is all green with evals passing, since after this comment the sweep label will no longer automatically kick off new sweeps. Remove and re-add the label to force one.

添加 H200 MTP 配置。
@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 关于重新运行失败任务的文档

补充性能变更日志中的 PR 链接。
Comment thread perf-changelog.yaml Outdated
- agentic-coding
description:
- "Add Qwen3.5 FP8 H200 SGLang AgentX MTP points with DRAM HiCache"
- "Use TP8/EP1 concurrency 2 through 24, published FlashInfer 0.6.15 CUDA 13 wheels, and golden MTP acceptance length 3.39"

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.

🟡 The new perf-changelog.yaml entry sets pr-link to https://github.com/SemiAnalysisAI/InferenceX/pull/XXX instead of the actual PR number. docs/configuration-procedures.md only permits the literal placeholder pr-link: TBD before a PR exists, to be replaced with the real URL immediately after PR creation — since this PR already exists as #2592, the entry should read pull/2592.

Extended reasoning...

The new tail entry appended to perf-changelog.yaml (line 5929) ends with:

pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX

docs/configuration-procedures.md documents the changelog-append procedure precisely: the template at line 251 shows pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/<number>, and line 254 explicitly states: "Before the PR exists, the model+hardware playbook permits pr-link: TBD. Replace it with the real URL immediately after creating the PR." The only sanctioned placeholder is the literal string TBD — not a URL with a literal XXX substituted for the PR number.

Why this isn't caught elsewhere: nothing in the repo's YAML schema or CI validates that pr-link matches pull/\d+, so a stray XXX placeholder parses fine as valid YAML and doesn't fail any automated check. The only enforcement mechanism is the documented convention plus the stop-condition in the same doc (line 272): "...or still has TBD when the PR is otherwise ready for sweep." That stop condition is phrased around the literal TBD placeholder, so a pull/XXX link technically slips past it too, even though it's just as unresolved as TBD would be.

Step-by-step proof:

  1. Every other entry in perf-changelog.yaml (e.g., lines for PRs perf(qwen3.5-fp4-b200-sglang-mtp): add TEP2 arm on NVFP4-V2 / perf(qwen3.5-fp4-b200-sglang-mtp): 基于 NVFP4-V2 添加 TEP2 组合 #2550, Add DSV4 B200 disaggregated Dynamo SGLang MTP configuration / 新增 DSV4 B200 分离式 Dynamo SGLang MTP 配置 #2554, [AMD] [AgentX] Add MI355X Qwen3.5 FP4 SGLang MTP #2562, [AMD] [AGENTX] GLM-5.2 MTP5 tune: raise acc-len and drop hicache at low conc / GLM-5.2 MTP5 调优:提升接受率目标并在低并发下关闭 hicache #2570) uses a real numeric PR link: .../pull/2550, .../pull/2554, etc.
  2. This PR's own metadata identifies it as PR Add Qwen3.5 H200 MTP config / 新增 Qwen3.5 H200 MTP 配置 #2592, meaning the real PR number was known/knowable at diff-authoring time.
  3. The correct final value per the documented procedure is pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2592.
  4. As written, pull/XXX is neither the permitted pre-PR placeholder (TBD) nor a resolved, valid link — it's an artifact left over from the changelog template that was never filled in.

Impact: This breaks changelog traceability — anyone (or any tooling) later using pr-link to trace a config change back to its originating PR will hit a dead/invalid URL (.../pull/XXX) instead of the real PR. It doesn't fail the benchmark sweep or any executable check, so it's not merge-blocking, but it should be corrected before merge since the PR number is already known.

Fix: Change line 5929 from pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/XXX to pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2592.

@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

@@ -0,0 +1,160 @@
#!/usr/bin/env bash
set -euo pipefail
set -x

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

dont we already have an qwen3.5_fp8_h200_mtp.sh file, can u edit that instead of creating an new one?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@github-actions

Copy link
Copy Markdown
Contributor

更新 SGLang 镜像。
@github-actions

Copy link
Copy Markdown
Contributor

更新 FlashInfer 版本。
@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.

2 participants