Repository navigation
[Test] KVShard: Extend HiCache E2E with GLM accuracy coverage - #46789
Conversation
✅ Preview approved@hzh0425 approved a Mintlify preview for commit |
|
/rerun-test -c |
|
🚀 🚀 |
|
/rerun-test -c |
|
⛔ Please ask a maintainer to run this command, or use the normal CI flow. |
|
/rerun-test -c |
|
🚀 |
|
/rerun-test -c |
|
🚀 |
|
There's no need to run CI tests for this PR. I have removed its |
|
/rerun-test -c |
|
🚀 |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Motivation
Follow up on the accuracy-test request in #42973. Extend the existing
test_dsa_glm52_pd_kv_shard_hicache.pywith GSM8K accuracy coverage for KV sharding and CPU HiCache together.Modifications
base-c / 4-gpu-gb300registration for the existing reload regression and both accuracy cases. All use P2/D2 with prefill CP2; decode uses GPUs 2–3. Retain the known GB300 fabric transport and exportable allocator:MC_FORCE_MNNVL=true,SGLANG_MOONCAKE_CUSTOM_MEM_POOL=NVLINK, staging disabled.Accuracy Tests
Local validation using the project
.venv:On head
e19de3aef0, the four-GB300 hardware job passed the reload regression and the full GSM8K test, scoring 0.9438029253271748 >= 0.935, including its H2D and MTP assertions. Mixed-MoE failed during decode setup: target + draft weights required a static-memory fraction above approximately 0.870, exceeding the inherited 0.85 budget. This change overrides only Mixed-MoE decode to 0.90, retaining the 65,536-token KV cap and accuracy floors; parser checks and pre-commit pass. The corrected Mixed-MoE case still needs hardware verification. The CI time estimate remains 600 seconds.Speed Tests and Profiling
Test and documentation changes only; no inference runtime changes or performance claims.
Checklist
CI States
Latest PR Test (Base): ❌ Run #40681717071
Latest PR Test (Extra): ❌ Run #40681717003
Latest PR Test (AMD ROCm 10): ❌ Run #40681717107