You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Validation: 8x H100 SXM (NV18) passed the BF16 dispatch -> prefetch -> compute -> combine correctness harness on 8 ranks with global_ok=true, max_abs_err=0.0, relative_err=0.0.
Docker/NCU note: suitable H100 Vast.ai hosts were container instances without Docker/NVIDIA Container Toolkit; host NCU counters were restricted, so no NCU performance claims are made.
Quick design question coming out of reviewing #33249: what do we want the MoonEP + batch-overlap (BTO) contract to be in SGLang?
The current PoC routes MoonEP through MaybeTboDeepEPDispatcher. When TBO is enabled, that wrapper creates two MoonEPDispatcher instances. At the same time, both dispatchers appear to resolve the process wide MoonEPBuffer using the same static key (shape/topology + process group), so they would reuse the same underlying moonep.Buffer.
I may be missing some intended MoonEP semantics here, so wanted to check with the team before treating this as a bug:
Is the intended near-term contract that MoonEP is synchronous/eager only and TBO/SBO should be explicitly disabled for now?
Or do we expect a single MoonEP buffer to safely support the multiple in-flight plans needed by TBO, in which case the SGLang adapter should be designed around that lifecycle?
My instinct for the current PoC would be to keep the supported surface narrow: disable overlap first, then add it once the buffer/plan ownership model is explicit. But I would love to understand the intended direction.
Activity
foraxe commentedon Jul 29, 2026
Maybe we could also explore some of these approaches:
foraxe commentedon Jul 30, 2026
kpham-sgl commentedon Jul 31, 2026
Hi @foraxe, we can keep the discussions under #29736
foraxe commentedon Jul 31, 2026
Got it. Thank you.
wirybeaver commentedon Aug 2, 2026
BF16 MoonEP PoC handoff is ready for the Kimi-K3 roadmap item.
NV18) passed the BF16 dispatch -> prefetch -> compute -> combine correctness harness on 8 ranks withglobal_ok=true,max_abs_err=0.0,relative_err=0.0.nvpohanh commentedon Aug 5, 2026
Will #32281 cover this?
charliechenye commentedon Aug 12, 2026
Quick design question coming out of reviewing #33249: what do we want the MoonEP + batch-overlap (BTO) contract to be in SGLang?
The current PoC routes MoonEP through MaybeTboDeepEPDispatcher. When TBO is enabled, that wrapper creates two MoonEPDispatcher instances. At the same time, both dispatchers appear to resolve the process wide MoonEPBuffer using the same static key (shape/topology + process group), so they would reuse the same underlying moonep.Buffer.
I may be missing some intended MoonEP semantics here, so wanted to check with the team before treating this as a bug:
My instinct for the current PoC would be to keep the supported surface narrow: disable overlap first, then add it once the buffer/plan ownership model is explicit. But I would love to understand the intended direction.
liuqi-1 commentedon Aug 13, 2026
I only implemented PP+DSpark. It needs some adaptions to support PD.