In a reported 80B total, roughly 3B active MoE comparison, HySparse2 uses 5.02× fewer prefill FLOPs and 2.69 GB rather than 12.09 GB of KV cache at 1 million tokens versus Hybrid SWA. Its self decoder handles long input prefill; cross decoder layers share KV data and sparse selection results, while a forced window k...
Published byEdited with GPT-6 SolImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: How does Xiaomi’s HySparse2 architecture use a YOCO-style self-decoder and cross-decoder, KV Bridging, and token-level KV Reuse with a force. Article summary: HySparse2 is an architecture proposal for long, repeatedly extended agent contexts—not a new MiMo-V3 open-weight release. Its central idea is to avoid running every long prompt through every decoder layer while retaining. Topic tags: general, academic, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, char
Long-running agents often add large tool outputs to an already substantial history. HySparse2 is Xiaomi’s proposed architecture for making that growing context less expensive to process while retaining access to both recent and distant tokens. The released work is architecture research associated with plans for MiMo-V3, not evidence of a new MiMo-V3 open-weight release. 3
4
HySparse2 divides the model into a YOCO-style self-decoder and cross-decoder. The self-decoder processes the long input. Through KV Bridging, full-attention layers in the cross-decoder construct their keys and values from self-decoder hidden states. Because the cross-decoder’s KV data comes from those states, prefill of the existing long context can finish after the self-decoder rather than running that context through the cross-decoder too. The cross-decoder still participates when the model generates new tokens. 4
6
15
Within each cross-decoder hybrid block, KV Reuse lets sparse layers share the preceding full-attention layer’s KV cache and token-selection indices. HySparse2 selects individual tokens rather than blocks. It also forces recent tokens into the sparse selection, replacing a separate sliding-window-attention branch so local and selected distant tokens can use the same cache. Together, these choices target repeated cache storage and selection work without excluding nearby context. 4
6
15
For a reported matched MoE configuration with 80B total parameters and roughly 3B active per token, HySparse2’s prefill FLOPs at 1 million tokens are 5.02× lower than Hybrid SWA’s. The reported KV-cache sizes are 2.69 GB versus 12.09 GB, or about 4.5× smaller. Xiaomi also reports higher MRCRv2 and RULER-v2 retrieval scores and lower AgentPPL and LongPPL; a report of the evaluation says HySparse2 leads both HySparse and Hybrid SWA on the evaluated long-context retrieval tests. 6
15
One reported ablation holds the backbone and attention budget constant while changing block-level selection to token-level selection. On tests at 32k tokens or less, the report gives gains of 6.57 percentage points on RULER-v2, 8.14 points on two-needle MRCR-v2, and 5.55 points on GraphWalks. That supports the value of finer-grained selection in that setting; it does not isolate the contribution of KV Bridging, KV Reuse, or the forced local window. 6
The available evidence does not establish a numerical HySparse-versus-HySparse2 result at 1 million tokens, component-by-component gains for every mechanism, or whether the matched-model improvements persist at a larger model scale. Nor do the cited excerpts specify the precision behind the 2.69 GB cache figure, so it should not be presented as a verified FP8-specific measurement. Prefill FLOPs and cache size also should not be mistaken for measured production latency. 6
15
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
In a reported 80B total, roughly 3B active MoE comparison, HySparse2 uses 5.02× fewer prefill FLOPs and 2.69 GB rather than 12.09 GB of KV cache at 1 million tokens versus Hybrid SWA.
In a reported 80B total, roughly 3B active MoE comparison, HySparse2 uses 5.02× fewer prefill FLOPs and 2.69 GB rather than 12.09 GB of KV cache at 1 million tokens versus Hybrid SWA. Its self decoder handles long input prefill; cross decoder layers share KV data and sparse selection results, while a forced window keeps recent tokens available.