Fetching from the wire…
Public story · 2026-07-25 · high
The fix trims only the draft model's attention window, requires no retraining, and leaves accuracy untouched.
Why now: It's a fix teams can apply without retraining, right as more inference stacks push into million-token context windows.
Alagappan Valliappan's new paper found the built-in draft step in speculative decoding scans the full cache every step, becoming the costliest part at million-token context. At that length, the draft step can end up costing more than it saves, according to the paper. That matters for any inference stack running near a million tokens, since the fix recovers 28-44% of the wasted cost.
The fix borrows a StreamingLLM-style trick: a sliding window plus an attention sink, applied only to the draft's attention. That drops about 99% of the draft's KV cache entries at 1M-token context. It was tested across Qwen GDN-MoE at 35B and 122B parameters and a Mamba2-hybrid NoPE model at 120B, running in SGLang on a single GPU. That combination cut per-decode-step cost 28-44%.
It's lossless, not an approximation: the full-attention target model still verifies every token the draft proposes, so accuracy doesn't move. The KV entries dropped from the draft's window aren't wasted either. A ring buffer reclaims the 7.7-11% that never get read, at no cost to acceptance rate.
The bigger point here is that a step marketed as negligibly cheap turned out to dominate cost once context got long enough. That's worth remembering the next time an inference paper calls something free.
It's a fix teams can apply without retraining, which matters as more inference stacks push into million-token context.
Each link below shares sources, entities, or timing with this story.
The day-0 SGLang post dated August 26 gives the architecture the release megathread didn't: 125B main parameters plus a separate 51.2B Per-Layer Embedding table at about 95.4 GiB in BF16, 6B activated per token, 48 layers split 36 GDN linear attention and 12 QSA sparse attenti...
Wafer.ai ran K3 at TP8 on a single MI355X node: 952 tok/s aggregate, 118 tok/s single-stream decode, ~13k tok/s steady-state prefill after fixing missing PyTorch sampling functions and AITER MLA prefill kernels via SGLang and ROCm. Against a two-node TP16 B200 deployment that'...
Google released open-source Multi-Token Prediction (MTP) drafters for the Gemma 4 model family. The concept: pair a heavy target model (Gemma 4 31B) with a lightweight drafter that predicts several future tokens in parallel. The target model verifies the predictions in a singl...
Load Hijack modifies nothing but router weights in a checkpoint. When a private trigger appears, token-to-expert assignment concentrates on experts co-located on a single GPU, making it a straggler while peers idle (arXiv 2608.10614). Across three MoE families and four corpora...
Sebastian Raschka's July 28 teardown argues K3 is less exotic than the release framing suggests: a scaled production version of Kimi Linear with Kimi Delta Attention as the hybrid attention layer and LatentMoE compressing large linear layers by down-projection. The genuinely n...
Speculative decoding (a small draft model proposes tokens the target verifies in parallel) gives 2-5x latency wins, but only in memory-bound, low-batch regimes. At large batch sizes the GPU is already compute-bound, and the extra draft-and-verify work makes inference *slower*...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.