Back to AI News
arxiv

LoopVQ: Sub-1-bit KV Cache Quantization for Looped Transformers

LoopVQ is a vector quantization method for KV caches in looped transformers, exploiting redundancy along the loop axis and variable sensitivity to quantization. It achieves 0.5 bits per element, outperforming existing KV quantization methods on reasoning and retrieval tasks, and combined with TaSQ retains near-BF16 accuracy at 0.25 bits. Implemented in SGLang, it nearly halves decode latency at 32K context and boosts serving throughput up to 6.1x.

AI Brief

This paper presents a concrete, novel optimization for an emerging architecture class, with measurable efficiency gains and practical deployment in SGLang.

arXiv:2611.05304v1 Announce Type: cross Abstract: Looped transformers are a parameter-efficient alternative to standard transformers for language modeling. By reapplying the same layers across multiple loop steps, recent looped language models match the performance of non-looped models several times their size. While this architecture effectively reduces parameter memory, each loop step still stores its own keys and values, so the key-value (KV) cache grows linearly with the number of loop steps and becomes the main memory bottleneck. We observe that the KV cache of looped models is highly redundant along the loop axis and that the loop steps differ substantially in their sensitivity to quantization. Based on these observations, we propose $\textbf{LoopVQ}$, a KV cache vector quantization method for looped transformers that codes channels of multiple loop steps jointly, and fine-tunes the codebooks to match the output of the full-precision model. At 0.5 bits per element, LoopVQ outperforms existing KV cache vector quantization methods for standard LLMs on general, long chain-of-thought reasoning, and long-context retrieval tasks with Ouro and Huginn models. Its design is orthogonal to these methods, and combined with TaSQ, it retains much of the BF16 accuracy even at 0.25 bits per element. We also implement LoopVQ in SGLang, where it nearly halves the decode latency at a 32K-token context and raises the peak serving throughput by up to $4.3\times$ and $6.1\times$ on the 1.4B and 2.6B Ouro models compared to the BF16 baseline.
Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!