[AMD] dsv4-fp4-mi355x-atom: enable DPA at high concurrency, update image to atom0.1.4#1717
[AMD] dsv4-fp4-mi355x-atom: enable DPA at high concurrency, update image to atom0.1.4#1717seungrokj wants to merge 32 commits into
Conversation
…e image to atom0.1.4 - Enable --enable-tbo for ISL=1024/OSL=1024 at CONC>=1024 and ISL=8192/OSL=1024 at CONC>=256 - Update image to atom0.1.4_20260612 - Update ISL=8192 search-space to start at conc=4 and use DPA from conc=128 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you
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. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers. If additional help is needed, PR authors can reach out to core maintainers over Slack. |
2 similar comments
|
Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you
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. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers. If additional help is needed, PR authors can reach out to core maintainers over Slack. |
|
Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you
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. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers. If additional help is needed, PR authors can reach out to core maintainers over Slack. |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27416363770 |
…onc range - Pass --max-model-len to server using SERVE_MAX_MODEL_LEN - Add EVAL_ONLY path: compute eval context length via compute_eval_context_length - Extend conc-end to 8192 (isl=1024) and 4096 (isl=8192) in amd-master.yaml Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27417198968 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27418122192 |
1 similar comment
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27418122192 |
…sable max-model-len Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…m-seqs Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
can u rebase it so the sweep triggers? |
…e, enable max-model-len Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… remove stale entries Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27612720147 |
1 similar comment
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27612720147 |
…x mem frac Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…add TP4/TP8 conc lists for ISL8192 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 421313c. Configure here.
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27668862004 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27668923188 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27668950324 |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27669004948 |
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27669101609 |
…nch override Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27675672700 |
…/TP8/DPA Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27676739575 |
1 similar comment
|
see unofficial run visualizer at https://inferencex.semianalysis.com/inference?unofficialRun=27676739575 |
|
@functionstackx @cquil11 can you please merge this ? |
|
/reuse-sweep-run |
|
/merge-prs |

Summary
rocm/atom:rocm7.2.4_ubuntu24.04_py3.12_pytorch_release_2.10.0_atom0.1.4_20260612Motivation
Based on Pareto frontier analysis from ATOM runs 27367309656 and 27030375093,
Test plan
bash -nsyntax check passes ondsv4_fp4_mi355x_atom.sh🤖 Generated with Claude Code
Note
Medium Risk
Larger concurrency sweeps and new serving flags (TBO, index cache, higher mem util) can shift stability/OOM behavior on MI355X; the dev nightly image pin adds release drift versus the changelog’s atom0.1.4 note.
Overview
Updates dsv4-fp4-mi355x-atom to drop the day-0 “CONC=1 only” guard and move the container image to
rocm/atom-dev:nightly_202606161823. The fixed-seq-len search space now sweeps higher concurrency with DPA through conc 2048 on 1k/1k, and on 8k/1k adds explicit TP4/TP8 conc lists plus DPA from conc 128–2048 (replacing the narrower TP8 + DPA 64–512 grid).dsv4_fp4_mi355x_atom.shturns on DPA+TBO (--enable-tbo,GPU_MAX_HW_QUEUES=5) at high concurrency for those ISL/OS pairs, raises static GPU memory to 0.9, passes CUDA graph capture sizes, disables prefix caching, and addsuse_index_cache/index_topk_freqHF overrides. Eval-only runs can setEVAL_MAX_MODEL_LENviacompute_eval_context_length.perf-changelog.yamldocuments the config change (note: its image string references atom0.1.4, which does not match theatom-devnightly pin in the YAML diff).Reviewed by Cursor Bugbot for commit 4364ef9. Bugbot is set up for automated code reviews on this repo. Configure here.