-
Notifications
You must be signed in to change notification settings - Fork 243
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: DEP tuning + LMCache refresh #2378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
1818c53
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: DEP tuning + LMCache ref…
seungrokj e10d502
docs(perf-changelog): add dsv4-fp4-mi355x-vllm-agentic entry for #2378
seungrokj 1b1a6f1
Merge branch 'main' into amd/agentx_dsv4_vllm_0728
seungrokj 5237349
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: pin lmcache to v0.5.2 in…
seungrokj c605e76
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: size max-num-seqs per DP…
seungrokj 4bfe42a
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: derate gpu-mem-util to 0…
seungrokj 2da5c48
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: force lm-eval; switch ar…
seungrokj a649ac4
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: cut DEP8 max-num-batched…
seungrokj 554c46a
[AMD] [AGENTX] dsv4-fp4-mi355x-vllm-agentic: cap gpu-mem-util at 0.85…
seungrokj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 This PR bumps the
dsv4-fp4-mi355x-vllm-agenticimage tag, raisesdram-utilization(0.60→0.80), and rewrites the search-space inconfigs/amd-master.yaml, but no corresponding entry was appended toperf-changelog.yaml. Per AGENTS.md's 'Updating Docker images' section this entry is required — it's the mechanism that triggers the benchmark sweep for the changed config, so without it the PR's own stated test plan ('Full-sweep CI green') will not execute.Extended reasoning...
AGENTS.md's "Updating Docker images" section (around line 152) states explicitly: "Update the image tag in the relevant
configs/*-master.yamland/orbenchmarks/*.sh, update any related env vars / config params, and append aperf-changelog.yamlentry (required - triggers benchmarks)." AGENTS.md also documents the mechanism itself (line ~78):perf-changelog.yamlis read chronologically and drives which configs get benchmarked in a sweep; new entries must be appended to the end.This PR does exactly the class of change that section calls out: it bumps the
dsv4-fp4-mi355x-vllm-agenticimage (nightly-09663abde...→nightly-49f31d7c...), raisesdram-utilizationfrom0.60to0.80, and replaces the search-space with a single new DEP+lmcache arm atconc: 76(configs/amd-master.yaml:1518-1522). These are precisely "image tag" and "related config params" changes.The diff only touches two files:
benchmarks/single_node/agentic/dsv4_fp4_mi355x_vllm.shandconfigs/amd-master.yaml.perf-changelog.yamlis not modified anywhere in this PR, and the tail of that file has no entry referencing this PR ordsv4-fp4-mi355x-vllm-agentic— every other recent recipe-bump PR in the history (e.g. #2327, #2345, #2349, #2341, #2305) appended a corresponding changelog entry for the same kind of change. There is an older entry referencingdsv4-fp4-mi355x-vllm-agentic, but it belongs to the recipe's original creation (PR #2109) — since the changelog is append-only and read chronologically, that stale entry does not re-trigger a sweep for this PR's new image/config changes.Concrete consequence: per the documented trigger mechanism, the full-sweep CI will not pick up
dsv4-fp4-mi355x-vllm-agenticfor re-benchmarking as a result of this PR's changes, since nothing was appended to signal that this config needs a fresh run. That directly undermines the PR's own stated Test plan checkbox — "Full-sweep CI green fordsv4-fp4-mi355x-vllm-agentic" — which cannot be exercised through the normal trigger path without the changelog entry. The DEP tuning and LMCache refresh this PR is meant to validate would ship unvalidated by the sweep infrastructure.Fix: append a
perf-changelog.yamlentry at the end of the file fordsv4-fp4-mi355x-vllm-agentic, following the existing schema (config-keys / description / pr-link), describing the image bump,dram-utilizationchange, and search-space rewrite, so the sweep triggers correctly.