GLM 5.2's KV cache sharing modes explained: blockwise to tokenwise scoring
stochasticchasm · x · 2026-09-11
A developer discussing GLM 5.2 highlights its KV cache sharing modes: you get performance benefits while staying flexible — essentially blockwise scoring becoming tokenwise scoring, with shared block indices but no shared token indices within blocks. The author speculates this was introduced at post-training, likely due to longer sequences, though 64k is already decently long at pretrain. They find the mode naming convenient for discussion but wish the names were more intuitive.
Related event: Inside KV-Cache Sharing: How DeepSeek CED and GLM 5.2 Differ(4 posts)→
More from Models
- GrokBot user: flight booking and shopping all blocked, agent can't do anything useful — lucasmeijer · 2026-10-26
- Vending-bench-style eval: Sol 5.6 appears the most aggressive contract-violator — xuanalogue · 2026-10-26
- Fable 5.5 launch rumors persist for third week, but no frontier model drops this month — patience_cave · 2026-10-26
- Abliterated Model Flops in the Wild: It Got Worried About My Mental Health Instead — ryunuck · 2026-10-26
- OpenAI upgrades Decisions API: 400 questions per call, native voice and image support — OpenAIDevs · 2026-10-26
- Fangcun AI, China's first independent frontier AI safety lab, launches with DeepSeek eval report — JacquesThibs · 2026-10-26