C2: SOTA board — dense NVFP4 fused MoE is the SM120 MoE decode SOTA, not quadbit sparse#19
Conversation
…_gate4/glm_graph_gate for SOTA board
…code SOTA, not quadbit sparse
There was a problem hiding this comment.
Code Review
This pull request establishes the C2 SOTA board, comparing the quadbit sparse D2 policy against the dense NVFP4 fused MoE baseline on SM120 hardware. The results, documented across several new markdown files and logs, demonstrate that the dense baseline is 6-8x faster at decode and more memory-efficient, framing the sparse policy's value around quality preservation and cross-architecture graph transfer rather than decode speed. Code changes in harness/serve_dsv4.py add support for running this dense baseline. The review feedback is highly consistent and correct, pointing out several instances in the new documentation files where references to other markdown files should be formatted as relative links, and glob patterns should be wrapped in backticks.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Greptile SummaryThis PR adds the C2 same-harness SOTA board for dense NVFP4 fused MoE versus quadbit sparse D2. The main changes are:
Confidence Score: 5/5Safe to merge with minimal risk. The code change is a narrow harness selector, and the documentation values match the committed C2 logs. No actionable bugs or security issues were identified. No files require special attention.
What T-Rex did
Important Files Changed
Sequence Diagram%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
participant User as Modal CLI
participant Harness as serve_dsv4.py graph_gate4/glm_graph_gate
participant Env as Environment selectors
participant Plugin as qb_sm120 plugin
participant VLLM as vLLM engine
participant MoE as FlashInfer-CUTLASS NVFP4 MoE
User->>Harness: "run graph gate with baseline=dense_nvfp4"
Harness->>Env: "set QB_MOE=off, QB_GRAPH=1, QB_DENSE=nvfp4"
Harness->>VLLM: initialize captured LLM with same PPL/decode protocol
VLLM->>Plugin: load SM120 attention/DSA unblock
Plugin-->>VLLM: "leave MoE unpatched when QB_MOE=off"
VLLM->>MoE: execute native fused dense NVFP4 MoE
VLLM-->>Harness: emit PPL, decode tok/s, KV, graph pool metrics
Harness-->>User: record C2 dense baseline log and board row
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
participant User as Modal CLI
participant Harness as serve_dsv4.py graph_gate4/glm_graph_gate
participant Env as Environment selectors
participant Plugin as qb_sm120 plugin
participant VLLM as vLLM engine
participant MoE as FlashInfer-CUTLASS NVFP4 MoE
User->>Harness: "run graph gate with baseline=dense_nvfp4"
Harness->>Env: "set QB_MOE=off, QB_GRAPH=1, QB_DENSE=nvfp4"
Harness->>VLLM: initialize captured LLM with same PPL/decode protocol
VLLM->>Plugin: load SM120 attention/DSA unblock
Plugin-->>VLLM: "leave MoE unpatched when QB_MOE=off"
VLLM->>MoE: execute native fused dense NVFP4 MoE
VLLM-->>Harness: emit PPL, decode tok/s, KV, graph pool metrics
Harness-->>User: record C2 dense baseline log and board row
Reviews (2): Last reviewed commit: "fix(c2): correct DeepSeek D2 graph pool ..." | Re-trigger Greptile |
….08); doc-link review fixes
|
@greptile review |
Summary
C2 builds the final SM120 MoE SOTA board: a direct, controlled, same-harness comparison of the C1
sparse route-slot D2 policy against the strongest dense/NVFP4 baseline that actually runs on this hardware.
It answers the question C1 could not: is quadbit sparse MoE a decode SOTA? It is not. The board is doing
exactly its job — catching an overclaim before it reaches the headline.
What the board measures
Every row runs through the same harness (
graph_gate4/glm_graph_gate), the same PPL passage(mito80), the same decode-only formula (
63/(wall64-wall1)), the same graph mode (captured), andthe same memory accounting (vLLM per-worker logs). The only change between baseline and quadbit rows is
the MoE selector. The dense baseline is vLLM's native FlashInfer-CUTLASS fused NVFP4 MoE (
QB_MOE=off),with the plugin's attention/DSA unblock so the model loads at all (vanilla vLLM cannot init it on SM120).
New controlled harness knob (no kernel work):
baseline=dense_nvfp4→QB_MOE=off.Board (captured, same harness)
DSA native on all four rows (
sparse_mla_sm120_decode_dsv4/FLASHINFER_MLA_SPARSE_SM120); all coherent,drop=0. C1's 11.3× was measured against the crippled dequant loop (0.514 tok/s), not this dense path.
Verdicts
memory, larger graph pool, and −62% KV on GLM (236,672 vs 629,760 tokens).
downstream MC smoke is the metric: DeepSeek D2 −0.79 pt, GLM D2 −0.95 pt vs dense.
MoE decode SOTA.
What quadbit sparse MoE genuinely is (not overclaimed)
The only deployed 2:4-sparse FP4 MoE on SM120; training-free capability-preserving structural sparsity that
transfers across architectures (DeepSeek → GLM) and graph-captures with native DSA (downstream within
~1 pt); and a prefill/large-M kernel Pareto point (paper §5 — a microbench, not re-measured in serving
here). Not a decode-speed or decode-memory win.
Next bottleneck (precise, not softened)
At decode (M=1–2) the sparse serving path (fixed-cap device routing + per-expert 2:4
sparse_moe_mm_2lvlgroup_gemm_nvfp4anchor, under Python-level per-expert loops) is 6–8× slower than asingle autotuned fused NVFP4 grouped GEMM; the 2:4 advantage is a large-M bandwidth effect absent at
decode. The only missing piece is a kernel: a fused sparse grouped decode GEMM at tiny M, plus dropping
dual residency. That is genuine new CUDA — identified, not started (per the C2 guardrail).
Baselines that do not run on SM120 (reported, not hidden)
plugin unblock is what lets the dense baseline run at all.
Deliverables
docs/c2/{sota_board,deepseek_sota,glm_sota,verdict}.md; raw logsdocs/audit/logs/c2_*.log;claims_checklist.md§11;command_manifest.mdC2 block; README + paper §10.1/§12/abstract synced to thehonest C2 finding (rebuilt
paper.tex/paper.pdf, zero net new overfull boxes).Guardrails
No "production-wide SOTA" (the board shows the opposite for decode). No "beats dense FP4 generally". Failed
baselines reported. CUTLASS 80b sparse prior art preserved. No mismatched-PPL quality claim. No custom CUDA
started.
Merge checklist
gh pr merge --merge), never squash