Repository navigation
[Klaud Cold] Update DSR1 FP8 MI355X ATOM MTP image to v0.1.7 / [Klaud Cold] 将 DSR1 FP8 MI355X ATOM MTP 镜像更新至 v0.1.7 - #3915
Klaud-Cold wants to merge 2 commits into
Conversation
Pin rocm/atom-dev:nightly_202610080328 by digest; its OCI labels identify ATOM 0.1.7 at release commit a526f0d. 将 DSR1 FP8 MI355X ATOM MTP 镜像更新为 v0.1.7 发布构建,并按摘要固定。 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for the contribution!
中文感谢你的贡献!
|
|
Initial attempt · Passed · Run 38141170149 / attempt 1 · 2026-10-11 13:17 UTC
Next: Append the changelog entry and run the final full sweep. 中文初次尝试 · 已通过 · Run 38141170149 / attempt 1 · 2026-10-11 13:17 UTC |
记录 DSR1 FP8 MI355X ATOM MTP 镜像更新的 perf-changelog 条目。 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Final full sweep · Passed · Run 38142648266 / attempt 1 · 2026-10-11 14:15 UTC
Note: All rows: request errors unavailable.
Note: 1k/1k c4 TP8 EP1 c24d64, 1k/1k c8 TP8 EP1 f84cc2, 1k/1k c16 TP8 EP1 93b5ce, 1k/1k c32 TP8 EP1 1a341c, 1k/1k c64 TP8 EP1 4df1a8, 1k/1k c128 TP8 EP1 7853b7, 1k/1k c256 TP8 EP1 1147f0, 1k/1k c512 TP8 EP1 33d209: Single-turn 1k1k retired 2026-07-17 in #2263 after this baseline; excluded from coverage. Next: Mark ready for maintainer review. 中文最终完整 sweep · 已通过 · Run 38142648266 / attempt 1 · 2026-10-11 14:15 UTC |
|
View unofficial run (performance): https://inferencex.semianalysis.com/inference?unofficialRun=38142648266 View unofficial run (accuracy): https://inferencex.semianalysis.com/evaluation?unofficialRun=38142648266 |
|
validated · Repairs: 0 · Runs: 38141170149, 38142625880, 38142648266 中文validated · 修复次数:0 · 运行:38141170149, 38142625880, 38142648266 |
|
/use 38142648266 |
|
Claude finished @Klaud-Cold's task in 17s —— View job LGTM, no blocking issues found. |
|
@Klaud-Cold staged run 38142648266: https://inferencemax-app-git-staging-semianalysisai.vercel.app/inference?i_dates=2026-10-11~r38142648266 This run remains available across future |
| - dsr1-fp8-mi355x-atom-mtp | ||
| description: | ||
| - "Update ATOM image from v0.1.3 to the v0.1.7 release build (rocm/atom-dev:nightly_202610080328, digest-pinned)." | ||
| pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/3915 |
There was a problem hiding this comment.
🟡 (optional) Changelog entry says image was updated "to the v0.1.7 release build" but the actual image pinned in both YAMLs is rocm/atom-dev:nightly_202610080328, a nightly dev build with no v0.1.7 tag anywhere. Anyone reading perf-changelog.yaml later to find which release is running will be misled into believing a tagged v0.1.7 release is deployed when it's actually an untagged nightly/dev digest build. Fix: make the description match the actual reference, e.g. "Update ATOM image from v0.1.3 to nightly build rocm/atom-dev:nightly_202610080328 (digest-pinned)", dropping the unverifiable "v0.1.7 release build" claim.
Why this was flagged
perf-changelog.yaml:9544 adds config-keys: [dsr1-fp8-mi355x-atom-mtp] with description:9546 "Update ATOM image from v0.1.3 to the v0.1.7 release build (rocm/atom-dev:nightly_202610080328, digest-pinned)". The actual image set at 8k1k.yaml:6 and amd-master.yaml:533 is rocm/atom-dev:nightly_202610080328@ sha256:9c3070bb..., which is a nightly/dev tag, not a release tag, and no v0.1.7 string appears anywhere in the diff. A later engineer or on-call reading the changelog to understand provenance of a regression will believe a stable v0.1.7 release is running and rule out nightly-build instability as a cause. No CI check cross-validates changelog description text against the image string, so nothing catches this mismatch before merge.
Verification: nit. The changelog entry at inferencex-e2e/perf-changelog.yaml:9545 reads "Update ATOM image from v0.1.3 to the v0.1.7 release build (rocm/atom-dev:nightly_202610080328, digest-pinned)." but the image actually pinned at inferencex-e2e/benchmarks/single_node/srt-slurm-recipes/dsr1/atom/mi355x-fp8-mtp/8k1k.yaml:6 and inferencex-e2e/configs/amd-master.yaml:535 is rocm/atom-dev:nightly_202610080328@ sha256:9c3070bb..., a nightly dev-channel build, not a "release build".
Goal: Update ATOM image from
rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.3torocm/atom-dev:nightly_202610080328@sha256:9c3070bb7d2600d2e1bcfd03cf5f71e4dc0941f3e1d20d3a5845056aae2334eb.Baseline: 2026-06-02 ·
rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.3Mean latency · Sources: API 1, API 2, API 3
Note: 1k/1k c4 TP8 EP1 c24d64, 1k/1k c8 TP8 EP1 f84cc2, 1k/1k c16 TP8 EP1 93b5ce, 1k/1k c32 TP8 EP1 1a341c, 1k/1k c64 TP8 EP1 4df1a8, 1k/1k c128 TP8 EP1 7853b7, 1k/1k c256 TP8 EP1 1147f0, 1k/1k c512 TP8 EP1 33d209: Single-turn 1k1k retired 2026-07-17 in #2263 after this baseline; excluded from coverage.
中文
**目标:**将 ATOM 镜像从
rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.3更新为rocm/atom-dev:nightly_202610080328@sha256:9c3070bb7d2600d2e1bcfd03cf5f71e4dc0941f3e1d20d3a5845056aae2334eb。**基线:**2026-06-02 ·
rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.3平均延迟 · 来源: API 1, API 2, API 3;数值及异常说明见上表。