Skip to content

Releases: ROCm/ATOM

v0.1.6-rc0

v0.1.6-rc0 Pre-release
Pre-release

Choose a tag to compare

@sunway513 sunway513 released this 04 Jul 17:22
f9017b5

ATOM v0.1.6 release candidate 0. Paired with AITER v0.1.17-rc0.

Wheels (3): rocm 7.0/7.1/7.2 (pure-python, py3-none-any)

atom-0.1.6rc0+rocm7.{0,1,2}-py3-none-any.whl — versioned per-rocm to pair with the matching aiter v0.1.17-rc0 wheel.

Base

main @ f9017b5. Includes the fastapi<0.137 cap (avoids prometheus-instrumentator serve-startup crash) and the MiniMax qknorm/backends fixes already on main.

Validation (paired with aiter v0.1.17-rc0, 5-model GSM8K 3-shot, MI355X)

DSR1 0.9507 / GLM-5 0.9371 / Kimi 0.9325 / MiniMax-M2.5 x3 mean 0.934 / Qwen3-235B x3 mean 0.875 — 9/9 PASS.

Note: GLM-5 requires aiter v0.1.17 #4064 (gluon mqa fix); serve GLM-5/large models with modest client concurrency to avoid first-request warmup timeouts.

v0.1.5

Choose a tag to compare

@sunway513 sunway513 released this 22 Jun 18:03
b0071c5

ATOM v0.1.5 — paired with AITER v0.1.16.

Paired container

rocm/atom-dev:atom0.1.5-aiter0.1.16 (ROCm 7.2.4 base, gfx942;gfx950, aiter @ 0730b33f)

Key fixes (vs v0.1.4)

  • MiniMax-M2.5 torch.compile: restore the qkv.shape[0] <= 256 shape guard on the fused qknorm-allreduce path (#1299). Without it the fused custom collective runs unconditionally at TP>1 inside the compiled attention forward, forcing a top-level graph break that re-enters VllmBackend and hard-fails engine init (VllmBackend can only be called once).
  • Compile-cache frozen-path guard: backends.py now skips any non-existent traced path (<frozen posixpath>, etc.) instead of only <string>/<frozen os> (#1299).
  • fastapi cap >=0.115,<0.137 to avoid prometheus-fastapi-instrumentator crash on serve startup (fastapi >=0.137 is now on PyPI) (#1221).

Validation

mi355-gpu-15, GSM8K 3-shot flexible-extract on the released container:

  • MiniMax-M2.5 0.9325, DeepSeek-R1-0528 0.9484 (smoke)
  • Full gate (pilot, same fixes): DSR1 0.952 / GLM5 0.947 / Kimi 0.940 / MiniMax 3x mean 0.929 / Qwen3 3x mean 0.871

v0.1.4

Choose a tag to compare

@sunway513 sunway513 released this 06 Jun 20:01

ATOM v0.1.4

First ATOM release in the bi-weekly paired-release cadence with AITER (see cadence proposal). Also the first ATOM release that uses a release-branch workflow (prior versions tagged directly off main).

Same commit as v0.1.4-rc0 (26f23a0b) — zero delta after 3-day RC soak with no partner issues filed against the RC.

Paired AITER version

ATOM v0.1.4 pairs with AITER v0.1.15. The two releases share commit history and were jointly validated 5/5 PASS on GSM8K (mi355-gpu-15).

Commits since v0.1.3

26f23a0  Revert "Qwen3.5-35B-A3B-FP8: GDN decode lossy fast path + fused MRoPE QK (#838)"
f51d7be  Revert "Remove qkv 256 tok limitation (#999)"
e3c97b9  Remove qkv 256 tok limitation (#999)             ← reverted
4c4ae4f  fix(spec_decode): support DP attention with MTP in Deepseek V4 (#1001)
dfb8eda  Qwen3.5-35B-A3B-FP8: GDN decode lossy fast path + fused MRoPE QK (#838) ← reverted
6260cc1  Debug 'no such file or directory benchmark_matrix.json' (#994)
11be15e  [atom-vllm benchmark] refine model case name (#995)
9f9e97b  Debug name 'AWS_P0' is not defined (#991)

Highlights (net effective changes from v0.1.3)

  • fix(spec_decode): DP attention with MTP support in DeepSeek-V4 (#1001)
  • CI/benchmark fixes: AWS_P0 env, model case names, benchmark_matrix.json (#991 / #994 / #995)

Cherry-pick exclusions (intentional)

Two PRs reverted from v0.1.4 during joint validation:

  • #999 (minimax qkv 256 tok limit): caused MiniMax-M2.5 server crash in joint test with AITER v0.1.15 (VllmBackend can only be called once). Will revisit in v0.1.5.
  • #838 (Qwen3.5 GDN + fused MRoPE QK): reverted from v0.1.4 cycle to keep Kimi-K2.5 accuracy unaffected. Will revisit in v0.1.5.

Joint validation (paired with AITER v0.1.15)

GSM8K 3-shot flexible-extract, MI355X (gfx950), ATOM stack on 26f23a0b + AITER wheel 0.1.15rc0+rocm7.1.manylinux.2.28-cp312:

Model Score Threshold Result
DeepSeek-R1-0528 (TP=8, fp8 KV) 0.9537 0.94 PASS
MiniMax-M2.5 (TP=2, fp8 KV) 0.9318 0.92 PASS
Qwen3-235B-A22B-FP8 (TP=8, fp8 KV) 0.8681 0.87 PASS (borderline)
GLM-5-FP8 (TP=8, fp8 KV) 0.9409 0.93 PASS
Kimi-K2.5-MXFP4 (TP=4, fp8 KV) 0.9219 0.92 PASS

5/5 PASS by upstream-canonical thresholds.

Container

Production: rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.4 (will be published after Nightly Docker Release workflow completes, ETA tonight)

Paired-pilot dev pin (immediate use): rocm/atom-dev:atom0.1.4-aiter0.1.15

Both ship the paired AITER v0.1.15 wheel pre-installed with matching triton 3.6.0 + flydsl 0.1.9.dev599.

Source

git clone --branch v0.1.4 https://github.com/ROCm/ATOM

Known issues

  • Qwen3 borderline accuracy (0.8681 vs threshold 0.87): single-question swing within GSM8K 3-shot noise band. Tracking for v0.1.5.
  • Kimi accuracy lower than ATOM HEAD upstream (0.9219 vs upstream-current 0.9393): root cause not fully bisected; possibly residual from #1001 DSv4 MTP change interaction with Kimi MoE path. Above threshold but below historical baseline. Will continue investigation in v0.1.5.

Feedback

ATOM v0.1.4-rc0

ATOM v0.1.4-rc0 Pre-release
Pre-release

Choose a tag to compare

@sunway513 sunway513 released this 06 Jun 02:14

ATOM v0.1.4-rc0

First release candidate for ATOM v0.1.4. Cut from release/v0.1.4 at 26f23a0b. This is the first ATOM release that uses a release branch workflow (prior versions tagged directly off main) and the first ATOM release paired with an AITER release in the bi-weekly cadence pilot (see ATOM bi-weekly release cadence proposal).

Final promotion (v0.1.4) planned for 2026-06-08 (~2 days RC soak).

Paired AITER version

ATOM v0.1.4-rc0 is validated to pair with AITER v0.1.15-rc0 (ABI-fixed wheels uploaded 2026-06-05).

Commits since v0.1.3

26f23a0  Revert "Qwen3.5-35B-A3B-FP8: GDN decode lossy fast path + fused MRoPE QK (#838)"
f51d7be  Revert "Remove qkv 256 tok limitation (#999)"
e3c97b9  Remove qkv 256 tok limitation (#999)             ← reverted
4c4ae4f  fix(spec_decode): support DP attention with MTP in Deepseek V4 (#1001)
dfb8eda  Qwen3.5-35B-A3B-FP8: GDN decode lossy fast path + fused MRoPE QK (#838) ← reverted
6260cc1  Debug 'no such file or directory benchmark_matrix.json' (#994)
11be15e  [atom-vllm benchmark] refine model case name (#995)
9f9e97b  Debug name 'AWS_P0' is not defined (#991)

Highlights (net effective changes from v0.1.3)

  • fix(spec_decode): DP attention with MTP support in DeepSeek-V4 (#1001)
  • CI/benchmark fixes: AWS_P0 env, model case names, benchmark_matrix.json (#991 / #994 / #995)

Cherry-pick exclusions (intentional)

Two PRs that landed on release/v0.1.4 were reverted during joint validation with AITER v0.1.15:

  • #999 (minimax qkv 256 tok limit): caused MiniMax-M2.5 server crash in joint test with v0.1.15 (VllmBackend can only be called once). Reverted; will revisit in v0.1.5.
  • #838 (Qwen3.5 GDN + fused MRoPE QK): kept in tree for Qwen3.5-35B-A3B-FP8 but reverted from v0.1.4 cycle to keep Kimi-K2.5 accuracy unaffected by the MRoPE path change. Will revisit in v0.1.5.

Joint validation (paired with AITER v0.1.15-rc0)

GSM8K 3-shot flexible-extract, MI355X (gfx950), ATOM stack on 26f23a0b + AITER wheel 0.1.15rc0+rocm7.1.manylinux.2.28-cp312:

Model Score Threshold Result
DeepSeek-R1-0528 (TP=8, fp8 KV) 0.9537 0.94 PASS
MiniMax-M2.5 (TP=2, fp8 KV) 0.9318 0.92 PASS
Qwen3-235B-A22B-FP8 (TP=8, fp8 KV) 0.8681 0.87 PASS (borderline)
GLM-5-FP8 (TP=8, fp8 KV) 0.9409 0.93 PASS
Kimi-K2.5-MXFP4 (TP=4, fp8 KV) 0.9219 0.92 PASS

5/5 PASS by upstream-canonical thresholds.

Install / use

Container build paired with this RC will be pushed to rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.4-rc0 after Lingpeng cuts it. Until then, use the source tag:

git clone --branch v0.1.4-rc0 https://github.com/ROCm/ATOM

Pair with AITER:

pip install   --extra-index-url https://rocm.frameworks-devreleases.amd.com/whl-staging/gfx942-gfx950/   https://github.com/ROCm/aiter/releases/download/v0.1.15-rc0/amd_aiter-0.1.15rc0+rocm7.1.manylinux.2.28-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Known issues

  • Qwen3 borderline accuracy (0.8681 vs threshold 0.87): single-question swing within GSM8K 3-shot noise band. Tracking for v0.1.5.
  • Kimi accuracy lower than ATOM HEAD upstream (0.9219 vs upstream-current 0.9393 on SGLang side): root cause not fully bisected; possibly residual from #1001 DSv4 MTP change interaction with Kimi MoE path. Above threshold but below historical baseline. Will continue investigation in v0.1.5.

Next steps

  • 2 days RC soak with paired AITER v0.1.15-rc0
  • 2026-06-08: promote v0.1.4-rc0v0.1.4 (final, Latest) if no partner issues raised
  • v0.1.5 / AITER v0.1.16 next cycle: revisit #999 + #838 fixes, investigate Kimi delta

Feedback

— Peng + Lingpeng


Container image

Paired all-inclusive image is being pushed (~50GB) to:

rocm/atom-dev:atom0.1.4-rc0-aiter0.1.15-rc0

Contents:

  • ATOM source at v0.1.4-rc0 (commit 26f23a0b)
  • AITER wheel: amd_aiter-0.1.15rc0+rocm7.1.manylinux.2.28-cp312
  • triton 3.6.0
  • flydsl 0.1.9.dev599 (from AMD nightlies mirror)
  • Base: rocm/atom:rocm7.2.2_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.2.post

Usage:

docker pull rocm/atom-dev:atom0.1.4-rc0-aiter0.1.15-rc0
docker run -dt --privileged --device=/dev/kfd --device=/dev/dri   --shm-size=64g --ipc=host   -v /path/to/models:/data   --name atom_v014_rc0   rocm/atom-dev:atom0.1.4-rc0-aiter0.1.15-rc0 sleep infinity

No partner-side flydsl/triton install needed — both baked into the image.

v0.1.3

Choose a tag to compare

@valarLip valarLip released this 31 May 03:01
bdcc62e

What's Changed

Read more

v0.1.2

Choose a tag to compare

@valarLip valarLip released this 30 Mar 04:20
0079204

What's Changed

Read more