Skip to content

[AMD][AgentX] DSv4 MI355X agentic disagg: add high-concurrency dots using DEP8#2308

Open
ichbinblau wants to merge 5 commits into
mainfrom
amd/agentx-v1.0-th-hicon-dpa
Open

[AMD][AgentX] DSv4 MI355X agentic disagg: add high-concurrency dots using DEP8#2308
ichbinblau wants to merge 5 commits into
mainfrom
amd/agentx-v1.0-th-hicon-dpa

Conversation

@ichbinblau

@ichbinblau ichbinblau commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Summary

Follow-on fixes for the DSv4 FP4 MI355X SGLang PD-disaggregated agentic benchmark (dsv4-fp4-mi355x-sglang-disagg-agentic-hicache), rebased on top of current main (which already absorbed the bulk of this branch's earlier history via #2170). Two logical changes:

  • HiCache sizing / NCCL / image / cudagraph fixes for the DSv4 agentic disagg recipe
  • DPA config update + RDMA/GPU pre-flight gates + router policy fix

What's changed

HiCache sizing (ratio vs size)

  • dsv4_fp4_mi355x_sglang-disagg.sh: set HICACHE_RATIO=4 and FORCE_HICACHE_RATIO=1 so this recipe explicitly opts into ratio-based sizing.
  • job.slurm: forward FORCE_HICACHE_RATIO into the container's HiCache env file (hicache_mc_<job>.env) alongside the other HICACHE_* vars — it was previously silently dropped, so the override never reached the server.

NCCL / decode cuda-graph crash workaround

  • models.yaml: disable prefill cuda-graph (disable_cuda_graph: true) for DeepSeek-V4-Pro-AgentX as a complementary mitigation, drop --enable-two-batch-overlap from dp_flags, lower prefill mem_fraction_static 0.8→0.72 and no-dp max_running_requests 128→64.
  • Recipe image bump: lmsysorg/sglang-rocm:v0.5.14-rocm720-mi35x-20260710v0.5.15.post1-rocm720-mi35x-20260719.

RDMA QoS/DCQCN + GPU-sanity pre-flight gates (job.slurm)

  • New helpers/rdma_check.sh: validates NIC QoS (PFC/DSCP) and DCQCN configuration on every allocated node via srun before any container/GPU time is spent. A misconfigured NIC otherwise only shows up much later as unexplained tail latency or throughput variance under MoRI cross-node KV transfer. Override with SKIP_RDMA_CHECK=1.
  • New helpers/gpu_sanity.sh: after container pre-clean/teardown, fails fast (naming the offending process) if a bare, non-containerized process is still holding GPU VRAM — instead of surfacing as an opaque OOM during model load ~30 minutes later.

Router policy fix + DPA (ep=8/dp-attn) hicache arm

  • server_sglang.sh (agentic branch only — DI branch untouched): fixes a bug where the script read ROUTER_PREFILL_POLICY but recipe scripts export PREFILL_ROUTER_POLICY, so the recipe's policy override was silently ignored and the router always fell back to the hardcoded default. Also switches the default prefill router policy from cache_awareconsistent_hashing, adds --dp-aware to the router flags, and comments out the separate --decode-policy override (superseded by --dp-aware).
  • configs/amd-master.yaml: bump dsv4-fp4-mi355x-sglang-disagg-agentic-hicache image to v0.5.15.post1-rocm720-mi35x-20260719; re-enable (previously commented out) the TP8/EP8/DPA (ep=8, dp-attn=true) hicache search-space arm at conc-list: [64, 96, 128].
  • trace_replay.sh: when PREFILL_ENABLE_DP=true, export AIPERF_HTTP_X_SMG_ROUTING_KEY_FROM_CORRELATION_ID=true so aiperf's HTTP routing key is derived from the correlation ID under DP-attention.

Test plan

  • bash -n on all touched shell scripts (env.sh, job.slurm, server_sglang.sh, setup_deps.sh, helpers/gpu_sanity.sh, helpers/rdma_check.sh) — syntax OK
  • configs/amd-master.yaml, benchmarks/multi_node/amd_utils/models.yaml — YAML parses cleanly
  • Diffed against origin/main to confirm no unintended regression in the IS_AGENTIC/DI router split or the router-readiness canary (wait_or_die) added in a prior PR
  • CI: e2e Test - dsv4-fp4-mi355x-sglang-disagg-agentic-hicache (multi-node, mi355x-amds) — new TP8/EP8/DPA arm at conc 64/96/128

ichbinblau and others added 2 commits July 23, 2026 06:45
…fill cudagraph for DSv4 agentic disagg

Co-authored-by: Cursor <cursoragent@cursor.com>
…x router policy env var/name

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

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 关于重新运行失败任务的文档

1 similar comment
@github-actions

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 关于重新运行失败任务的文档

@ichbinblau ichbinblau changed the title [AMD][AgentX] DSv4 MI355X agentic disagg: HiCache/router fixes, RDMA+GPU pre-flight gates, DPA (ep=8/dp-attn) hicache arm [AMD][AgentX] DSv4 MI355X agentic disagg: add high-concurrency dots using DEP8 Jul 23, 2026
Comment thread configs/amd-master.yaml
Comment thread benchmarks/multi_node/amd_utils/models.yaml Outdated
Comment thread benchmarks/multi_node/amd_utils/server_sglang.sh
@ichbinblau ichbinblau added AMD agentx AgentX benchmarks, recipes, and infrastructure full-sweep-enabled labels Jul 23, 2026
@functionstackx

Copy link
Copy Markdown
Collaborator

hi @ichbinblau any chance u can priority doing disagg mtp for agentic

@ichbinblau

ichbinblau commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator Author

hi @ichbinblau any chance u can priority doing disagg mtp for agentic

Hi @functionstackx, this PR fixes the SGL router settings issues for high-concurrency use cases. I'll open another PR for the MTP changes.

ichbinblau and others added 2 commits July 23, 2026 08:00
…ic-hicache

Resolves review comment: the image bump (v0.5.14 -> v0.5.15.post1),
re-enabled TP8/EP8/DPA hicache arm, and HiCache sizing/NCCL/router
fixes need a changelog entry to trigger the benchmark sweep on merge.

中文:为 dsv4-fp4-mi355x-sglang-disagg-agentic-hicache 添加 perf-changelog.yaml
条目。解决评审意见:镶像升级(v0.5.14 -> v0.5.15.post1)、重新启用的
TP8/EP8/DPA hicache 分支,以及 HiCache 容量/NCCL/路由策略修复,需要一条
changelog 条目才能在合并时触发基准测试扫描。

Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Theresa Shan <theresa.shan@amd.com>
@github-actions

Copy link
Copy Markdown
Contributor

Signed-off-by: Theresa Shan <theresa.shan@amd.com>
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

1 similar comment
@github-actions

Copy link
Copy Markdown
Contributor

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

Labels

agentx AgentX benchmarks, recipes, and infrastructure AMD full-sweep-enabled

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants