Skip to content

[Klaud Cold] Update MiniMax-M3 FP4 MI355X ATOM AgentX image to nightly_202610151507 / [Klaud Cold] 将 MiniMax-M3 FP4 MI355X ATOM AgentX 镜像更新至 nightly_202610151507 - #4171

Closed
Klaud-Cold wants to merge 1 commit into
mainfrom
klaud/auto-00ea2b38724916ae-347ebf35395d307a
Closed

[Klaud Cold] Update MiniMax-M3 FP4 MI355X ATOM AgentX image to nightly_202610151507 / [Klaud Cold] 将 MiniMax-M3 FP4 MI355X ATOM AgentX 镜像更新至 nightly_202610151507#4171
Klaud-Cold wants to merge 1 commit into
mainfrom
klaud/auto-00ea2b38724916ae-347ebf35395d307a

Conversation

@Klaud-Cold

@Klaud-Cold Klaud-Cold commented Oct 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Goal: Update ATOM image from rocm/atom-dev:nightly_202610070333 to rocm/atom-dev:nightly_202610151507.
Baseline: 2026-10-08 · rocm/atom-dev:nightly_202610070333
Mean latency · Sources: API 1, API 2

Point Total tok/s/GPU ↑ Output tok/s/GPU ↑ TTFT ms ↓ TPOT ms ↓
AgentX c1 TP2 EP1 d4aad2 9,387.24 67.32 718 3.75
AgentX c1 TP4 EP1 da047d 6,580.17 42.49 734.47 2
AgentX c2 TP2 EP1 a06156 9,867.55 81.39 602.2 4.03
AgentX c2 TP4 EP1 4b9dbc 6,981.07 50.79 463.16 2.06
AgentX c4 TP2 EP1 bc7f18 14,243.33 102.59 501.07 4.18
AgentX c4 TP4 EP1 bcbcb3 9,201.17 63.47 430.42 2.18
AgentX c5 TP4 EP1 d32861 10,158.02 75.92 427.99 2.4
AgentX c8 TP4 EP1 b77092 15,414.47 110.52 447.66 2.56
AgentX c10 TP4 EP1 76cb0c 18,046.82 132.62 460.4 2.9
AgentX c12 TP4 EP1 034954 17,870.03 139.15 339.47 3.29
AgentX c15 TP4 EP1 e50aa2 23,785.1 178.83 430.37 3.48
AgentX c20 TP2 EP1 c15b90 55,247.63 391.01 732.57 9.5
AgentX c20 TP4 EP1 484fcb 36,113.98 228.55 517.47 4.33
AgentX c24 TP4 EP1 499637 43,851.26 264.75 594.63 5.04
AgentX c25 TP2 EP1 4f02dc 66,873.04 448.34 971.96 12.24
AgentX c28 TP4 EP1 d42f03 47,013.38 291.05 766.82 6.11
AgentX c30 TP2 EP1 00a4a9 63,701.41 438.34 3,174.8 15.57
AgentX c40 TP4 EP1 27d61b 56,208.72 381.66 772.26 9.53
AgentX c48 TP4 EP1 c91a25 58,632.64 395.63 1,181.74 14.93
Eval Score ↑ Samples
minimax_m3_full/em_strict · c1 TP2 98% 102
minimax_m3_full/em_strict · c1 TP4 99% 102
minimax_m3_full/em_strict · c2 TP2 98% 102
minimax_m3_full/em_strict · c2 TP4 99% 102
minimax_m3_full/em_strict · c4 TP2 98% 102
minimax_m3_full/em_strict · c4 TP4 99% 102
minimax_m3_full/em_strict · c5 TP4 99% 102
minimax_m3_full/em_strict · c8 TP4 98% 102
minimax_m3_full/em_strict · c10 TP4 98% 102
minimax_m3_full/em_strict · c12 TP4 99% 102
minimax_m3_full/em_strict · c15 TP4 98% 102
minimax_m3_full/em_strict · c20 TP2 98% 102
minimax_m3_full/em_strict · c20 TP4 98% 102
minimax_m3_full/em_strict · c24 TP4 97% 102
minimax_m3_full/em_strict · c25 TP2 98% 102
minimax_m3_full/em_strict · c28 TP4 99% 102
minimax_m3_full/em_strict · c30 TP2 98% 102
minimax_m3_full/em_strict · c40 TP4 99% 102
gsm8k/em_strict · c48 TP4 96.89% 1,319
minimax_m3_full/em_strict · c48 TP4 99% 102
中文

**目标：**将 ATOM 镜像从 rocm/atom-dev:nightly_202610070333 更新至 rocm/atom-dev:nightly_202610151507。
**基线：**2026-10-08 · rocm/atom-dev:nightly_202610070333
平均延迟 · 来源： API 1, API 2；数值及异常说明见上表。

@github-actions @claude
chore(amd): update MiniMax-M3 MI355X ATOM AgentX image to nightly_202…
8351f67 
…610151507

Move minimaxm3-fp4-mi355x-atom-agentic-mtp to rocm/atom-dev:nightly_202610151507
(ATOM e6182e08b), pinned by digest, and drop ATOM_PA_FLYDSL_PLAN, which ATOM
#2514 removed (FlyDSL paged decode always uses its work planner).

将 minimaxm3-fp4-mi355x-atom-agentic-mtp 更新至 rocm/atom-dev:nightly_202610151507
（ATOM e6182e08b），按 digest 固定；并移除 ATOM #2514 已删除的 ATOM_PA_FLYDSL_PLAN
（FlyDSL paged decode 始终使用其 work planner）。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Thanks for the contribution!

  • Review: If this PR changes files owned by someone other than a repository admin or @SemiAnalysisAI/core, ask one eligible CODEOWNER to complete the latest PR_REVIEW_CHECKLIST.md before contacting a core maintainer on Slack. Follow the template exactly, including As a PR reviewer and CODEOWNER, I have reviewed this and have, so sign-off verification triggers.
  • PR verification: Sweeps run only when the PR appends an inferencex-e2e/perf-changelog.yaml entry and carries exactly one primary label: full-sweep-fail-fast (strongly recommended; canary plus per-matrix fail-fast), full-sweep-enabled (canary; matrix jobs continue after a failure), or non-canary-full-sweep-enabled (no canary or fail-fast). The modifiers all-evals, evals-only, and agentx-fast require a primary label. On fork PRs, a maintainer applies the label. See sweep labels and reuse.
  • After merging: PR authors must ensure all GitHub Actions jobs pass. Transient failures often pass on rerun; see how to rerun failed jobs.
中文

感谢你的贡献！

  • **审阅：**如果 PR 修改的文件归属于仓库管理员及 @SemiAnalysisAI/core 之外的 CODEOWNER，请先联系一位有资格的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md，再通过 Slack 联系核心维护者。必须严格遵循模板，并保留 As a PR reviewer and CODEOWNER, I have reviewed this and have，才能触发签核验证。
  • **PR 验证：**只有当 PR 在 inferencex-e2e/perf-changelog.yaml 末尾追加了条目，并且恰好带有一个主标签时，才会运行扫描：full-sweep-fail-fast（强烈推荐；canary 加逐矩阵 fail-fast）、full-sweep-enabled（有 canary；矩阵任务在失败后继续运行）或 non-canary-full-sweep-enabled（无 canary，也无 fail-fast）。修饰标签 all-evals、evals-only 和 agentx-fast 必须与主标签一起使用。fork PR 的标签由维护者添加。参见扫描标签与复用。
  • **合并后：**PR 作者必须确保所有 GitHub Actions 任务通过。临时性失败通常可以通过重新运行恢复；参见重新运行失败任务的说明。

@Klaud-Cold

Klaud-Cold commented Oct 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Initial attempt · Failed · Run 38875951964 / attempt 1 · 2026-10-16 11:53 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
Change: Measure 8351f67: move to nightly_202610151507 by digest (ATOM 7fc0926c6 to e6182e08b, Triton 3.7.0 to 3.8.0; ROCm 7.2.4, torch 2.10.0, LMCache v0.4.5 and Mooncake v0.3.14-rc1 unchanged) and drop ATOM_PA_FLYDSL_PLAN, removed by ROCm/ATOM#2514 (FlyDSL paged decode always plans, as the old default 1 did). ROCm/ATOM@7fc0926...e6182e0 removes no flag or env this recipe uses; MiniMax-M3 gets mono pad-row and indexer-CP stride fixes (ROCm/ATOM#2485). The image does not label its AITER commit, so the #5809 FlyDSL API is unverified (ATOM warns and uses gluon if absent). No engine patch.

Next: Rerun the whole run on the same head as infrastructure retry 1; this does not consume a recipe repair.

中文

初次尝试 · 失败 · Run 38875951964 / attempt 1 · 2026-10-16 11:53 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
**变更：**测量 8351f67：按 digest 迁移到 nightly_202610151507（ATOM 7fc0926c6 至 e6182e08b，Triton 3.7.0 至 3.8.0；ROCm 7.2.4、torch 2.10.0、LMCache v0.4.5 与 Mooncake v0.3.14-rc1 不变），并移除 ROCm/ATOM#2514 已删除的 ATOM_PA_FLYDSL_PLAN（FlyDSL paged decode 始终使用 planner，与旧默认值 1 一致）。ROCm/ATOM@7fc0926...e6182e0 未删除本配方使用的参数或环境变量；MiniMax-M3 获得 mono pad 行与 indexer-CP stride 修复（ROCm/ATOM#2485）。镜像未标注 AITER commit，#5809 FlyDSL API 未验证（缺失时 ATOM 告警并使用 gluon）。无引擎补丁。实测数值及异常说明见上表。
**下一步：**在同一提交上整体重跑该 run，作为第 1 次基础设施重试；不占用配方修复次数。

@Klaud-Cold

Klaud-Cold commented Oct 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Infrastructure retry 1 · Failed · Run 38875951964 / attempt 2 · 2026-10-16 12:34 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
Change: Rerun the same measured head 8351f67 unchanged after the Docker Hub HTTP 429 image-import failures of run attempt 1.

Eval Score ↑ Samples
minimax_m3_full/em_strict · c1 TP2 99% (+1.00 pp) 102 each
minimax_m3_full/em_strict · c1 TP4 99% (+0.00 pp) 102 each
minimax_m3_full/em_strict · c20 TP2 99% (+1.00 pp) 102 each
minimax_m3_full/em_strict · c40 TP4 99% (+0.00 pp) 102 each
gsm8k/em_strict · c48 TP4 96.82% (-0.08 pp) 1,319 each

Next: Rerun only the failed and cancelled benchmark jobs of this run on the same head as infrastructure retry 2, keeping the passed eval artifacts.

中文

基础设施重试 1 · 失败 · Run 38875951964 / attempt 2 · 2026-10-16 12:34 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
**变更：**在第 1 次 run attempt 出现 Docker Hub HTTP 429 镜像导入失败后，原样重跑同一测量提交 8351f67。实测数值及异常说明见上表。
**下一步：**在同一提交上仅重跑本 run 中失败和被取消的基准测试任务，作为第 2 次基础设施重试，并保留已通过的评测产物。

@Klaud-Cold

Klaud-Cold commented Oct 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator Author

Infrastructure retry 2 · Failed · Run 38875951964 / attempt 3 · 2026-10-16 14:09 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
Change: Rerun only the failed and cancelled smoke benchmark jobs at the same measured head 8351f67, reusing the five passed evals from run attempt 2.

Eval Score ↑ Samples
minimax_m3_full/em_strict · c1 TP2 99% (+1.00 pp) 102 each
minimax_m3_full/em_strict · c1 TP4 99% (+0.00 pp) 102 each
minimax_m3_full/em_strict · c20 TP2 99% (+1.00 pp) 102 each
minimax_m3_full/em_strict · c40 TP4 99% (+0.00 pp) 102 each
gsm8k/em_strict · c48 TP4 96.82% (-0.08 pp) 1,319 each

Next: Finish as failed, close this PR and release the family so a later wave can retry once the registry and Hub rate limits clear.

中文

基础设施重试 2 · 失败 · Run 38875951964 / attempt 3 · 2026-10-16 14:09 UTC
rocm/atom-dev:nightly_202610151507@sha256:aa6754256dd68009240e54206265e5250395374640f07757f2fdeac6170097cf · 12dbddac599f
**变更：**在同一测量提交 8351f67 上仅重跑失败和被取消的 smoke 基准测试任务，复用第 2 次 run attempt 中已通过的五项评测。实测数值及异常说明见上表。
**下一步：**以失败结束，关闭此 PR 并释放该配置族，以便在镜像仓库与 Hub 速率限制解除后由后续批次重试。

@Klaud-Cold

Klaud-Cold commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator Author

failed · Cleanup pending. Stop and confirm owned runs before closing.

中文

failed · 清理待完成。先停止并确认自有运行结束，再关闭 PR。

@Klaud-Cold Klaud-Cold closed this Oct 16, 2026
@Klaud-Cold
Klaud-Cold deleted the klaud/auto-00ea2b38724916ae-347ebf35395d307a branch October 16, 2026 14:09
@Klaud-Cold

Klaud-Cold commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator Author

failed · Repairs: 0 · Runs: 38875951964
All owned runs ended. PR closed; branch deleted for retry.

中文

failed · 修复次数：0 · 运行：38875951964
所有自有运行均已结束。PR 已关闭；分支已删除，可重新尝试。

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

Reviewers

@billishyahao billishyahao Awaiting requested review from billishyahao billishyahao will be requested when the pull request is marked ready for review billishyahao is a code owner
@chunfangamd chunfangamd Awaiting requested review from chunfangamd chunfangamd will be requested when the pull request is marked ready for review chunfangamd is a code owner
@seungrokj seungrokj Awaiting requested review from seungrokj seungrokj will be requested when the pull request is marked ready for review seungrokj is a code owner
@1am9trash 1am9trash Awaiting requested review from 1am9trash 1am9trash will be requested when the pull request is marked ready for review 1am9trash is a code owner
@zijiecode zijiecode Awaiting requested review from zijiecode zijiecode will be requested when the pull request is marked ready for review zijiecode is a code owner

Assignees

No one assigned

Labels

None yet

Projects

InferenceX Board
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Klaud-Cold