Skip to content

[Klaud Cold] kimik2.5-fp4-b200-vllm: v0.26.0 image, extend conc to 512, add DEP4 arm / 升级 B200 镜像至 v0.26.0,扩展并发,新增 DEP4 - #2443

Open
xinli-sw wants to merge 20 commits into
mainfrom
feat/kimik2.5-fp4-b200-vllm-v0.26.0
Open

[Klaud Cold] kimik2.5-fp4-b200-vllm: v0.26.0 image, extend conc to 512, add DEP4 arm / 升级 B200 镜像至 v0.26.0,扩展并发,新增 DEP4#2443
xinli-sw wants to merge 20 commits into
mainfrom
feat/kimik2.5-fp4-b200-vllm-v0.26.0

Conversation

@xinli-sw

@xinli-sw xinli-sw commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Image: v0.22.0vllm/vllm-openai:v0.26.0
  • TP arms: TP8 and TP4 extended to conc-end: 512
  • New DEP4 arm: tp: 4, ep: 4, dp-attn: true, conc-start: 128, conc-end: 512
  • Bench script (kimik2.5_fp4_b200.sh): DP_ATTENTION handling added — switches to --data-parallel-size, adds --enable-expert-parallel and --prefill-schedule-interval 4 in DEP4 mode

中文说明

  • 镜像v0.22.0vllm/vllm-openai:v0.26.0
  • TP 配置:TP8 和 TP4 并发上限均扩展至 conc-end: 512
  • 新增 DEP4 配置tp: 4, ep: 4, dp-attn: true, conc-start: 128, conc-end: 512
  • 基准脚本kimik2.5_fp4_b200.sh):新增 DP_ATTENTION 处理逻辑,DEP4 模式下切换为 --data-parallel-size,并启用 --enable-expert-parallel--prefill-schedule-interval 4

@github-actions

github-actions Bot commented Aug 1, 2026

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
- "Bump Kimi K2.5 NVFP4 B200 vLLM image from v0.22.0 to v0.26.0"
- "Extend TP8/TP4 concurrency sweep to 512"
- "Add DEP4 arm (tp4 ep4 dp-attn) with --prefill-schedule-interval 4, conc 128-512"
pr-link: TBD

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 changelog entry uses pr-link: TBD, but the placeholder validators only accept XXX or the canonical .../pull/XXX URL — any other value raises ChangelogValidationError. Please change it to pr-link: XXX, which gets auto-canonicalized to the real PR URL on merge.

Extended reasoning...

perf-changelog.yaml (line 5365) sets pr-link: TBD for the new Kimi-K2.5 FP4 B200 vLLM entry. This value is not one of the accepted placeholders used elsewhere in this same file (every other entry uses either XXX or the fully-qualified https://github.com/SemiAnalysisAI/InferenceX/pull/<N> URL).

utils/validate_perf_changelog.py defines PR_LINK_PLACEHOLDERS = {"XXX", "https://github.com/SemiAnalysisAI/InferenceX/pull/XXX"} (line 24). validate_added_pr_link (called from compare_entries for every newly appended entry when running in PR-context, i.e. pr_number is set) checks each new entry's pr-link against this set and against the expected canonical URL for the current PR. For link = "TBD", neither condition is satisfied, so it raises ChangelogValidationError("new PR entry must use {expected!r} or an XXX placeholder; found 'TBD'") at lines 156-160.

Independently, utils/prepare_perf_changelog_merge.py performs its own canonicalization pass during merge-prep (the step invoked by utils/merge_with_reuse.sh, the standard merge path for this repo). Lines 111-114 check the same PR_LINK_PLACEHOLDERS set and raise ChangelogValidationError(f"appended entry {index + 1} has unexpected pr-link {link!r}") if the link isn't a recognized placeholder — which TBD is not.

So this single value trips two separate, independent checks: PR-time changelog validation and merge-time canonicalization. Neither existing check is lenient enough to let an arbitrary human-readable placeholder like TBD through — they intentionally accept only XXX or the literal templated URL so that automation can reliably find-and-replace the placeholder with the real PR link at merge time.

Step-by-step proof:

  1. PR [Klaud Cold] kimik2.5-fp4-b200-vllm: v0.26.0 image, extend conc to 512, add DEP4 arm / 升级 B200 镜像至 v0.26.0,扩展并发,新增 DEP4 #2443 appends the entry at perf-changelog.yaml:5365 with pr-link: TBD.
  2. When validate_perf_changelog.py runs in CI for this PR (with pr_number=2443), it calls compare_entries(), which calls validate_added_pr_link(entry, pr_number=2443, ...) for this newly appended entry.
  3. Inside that function: expected = "https://github.com/SemiAnalysisAI/InferenceX/pull/2443". The check if link not in PR_LINK_PLACEHOLDERS and link != expected evaluates: "TBD" not in {"XXX", ".../pull/XXX"} → True, and "TBD" != expected → True, so the and is True → raises ChangelogValidationError.
  4. Even if that check were somehow bypassed, prepare_perf_changelog_merge.py (invoked by merge_with_reuse.sh during the actual merge) performs the same style of check on every appended entry and raises "appended entry N has unexpected pr-link 'TBD'" for the same reason.
  5. Either failure blocks the standard PR/merge automation for this repo.

Fix: change line 5365 from pr-link: TBD to pr-link: XXX (matching the convention used elsewhere in this file, e.g. other pending entries). The XXX placeholder is automatically canonicalized to the real pull/<PR-number> URL by the merge-prep tooling once the PR is merged, so no other action is required.

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Aug 2, 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.

1 participant