Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions configs/nvidia-master.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8991,15 +8991,15 @@ glm5.2-fp4-b300-sglang-agentic-mtp:
image: lmsysorg/sglang:v0.5.16-cu130
model: nvidia/GLM-5.2-NVFP4
model-prefix: glm5.2
runner: cluster:b300-nv
runner: cluster:b300-dsxe
precision: fp4
framework: sglang
multinode: false
scenarios:
Comment on lines 8991 to 8998

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 (optional) The doc comment above this recipe still says the concurrency grid has 'a hard stop at conc 16' and justifies omitting a DEP throughput arm because its frontier peak (48) is 'well above that cap' — but this diff raises conc-list to 48, so the stated cap is now exactly the DEP arm's peak and the omission rationale no longer holds. Fix: update the comment to reflect the new [1..48] grid and re-justify (or reconsider) excluding the DEP arm now that 48 is in-range, not just the conc-list value.

Extended reasoning...

Lines 8980-8989 explain the design rationale for this recipe; line 8991-8998 is the recipe itself. The diff only touches the runner and conc-list (lines 8994, 8998) but leaves the rationale comment unchanged, so a reader (or future engineer using the comment to decide whether to add a DEP arm) is told the grid stops at 16 and that DEP's peak (48) is safely above the cap, when in fact the recipe now measures exactly conc 48 without a DEP baseline for comparison — misleading future changes to this recipe.

Verification: nit. The finding is factually accurate but is a stale-comment issue, not a functional defect. The recipe's design-rationale comment (configs/nvidia-master.yaml:8980-8989) still reads "on the AgentX MTP concurrency grid [1, 4, 8, 12, 16]" (8981), "a hard stop at conc 16" (8983), and justifies omitting a DEP arm because "its measured frontier peak is conc 48, well above that cap"…

agentic-coding:
- dram-utilization: 0.80
search-space:
- { tp: 8, spec-decoding: mtp, kv-offloading: dram, kv-offload-backend: { name: hicache }, conc-list: [1, 4, 8, 12, 16] }
- { tp: 8, spec-decoding: mtp, kv-offloading: dram, kv-offload-backend: { name: hicache }, conc-list: [1, 4, 8, 12, 16, 20, 24, 28, 32, 40, 48] }

# First GLM-5.2 AgentX recipe on B200, shipped spec-decode-only per the AgentX
# policy that agentic arms enable speculative decoding rather than running a
Expand Down
9 changes: 9 additions & 0 deletions perf-changelog.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6878,3 +6878,12 @@
description:
- "Refresh the Kimi-K3 GB300 AgentX configurations with updated configs."
pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2811

- config-keys:
- glm5.2-fp4-b300-sglang-agentic-mtp
scenario-type:
- agentic-coding
description:
- "Extend the GLM-5.2 NVFP4 B300 SGLang AgentX MTP TP8 HiCache curve from concurrency 16 to 48 with new points at 20, 24, 28, 32, 40, and 48."
- "Move the recipe from the retired cluster:b300-nv fleet to cluster:b300-dsxe so the sweep can be generated and scheduled again."
pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/2829
Loading