- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper presents Elastic-QVG, a training-free method for reducing the KV-cache memory used by autoregressive video generation. It stores new history at higher precision and gradually reduces the precision of older history when the cache reaches a fixed memory budget. The proposed encoding allows stored values to lose bits without being re-quantized, and the bit-plane storage makes it possible to release the corresponding memory. Experiments on LongCat-Video, HY-WorldPlay, and LingBot-World show substantial memory savings and generally better quality than static QVG at comparable cache sizes.
Critical strengths
(1) Training-free and easy to adopt. The method does not require fine-tuning the video model or training a separate compression model. This lowers the cost of applying it to existing generators. Reducing precision directly on the stored cache also avoids repeated decoding and re-quantization.
(2) An elegant way to control KV-cache memory, with promising results. Gradually reducing precision provides a useful choice between keeping history at a fixed precision and deleting it. The proposed storage design turns this idea into actual memory savings. The reported quality results are also encouraging: Elastic-QVG generally preserves the original model’s outputs better than static QVG at comparable cache sizes.
Critical weaknesses
(1) Insufficient validation on long videos. Long-video generation is a main motivation of the paper, but the experiments do not sufficiently show whether quality remains stable during extended generation. Figure 10 demonstrates bounded memory usage, rather than the corresponding video quality, and the total video lengths used in the main quality comparisons are not consistently specified. Small quality losses over shorter sequences may grow as generation continues and older history is compressed or removed. Quality measurements over longer rollouts, especially after the cache reaches its memory budget, are needed to support the paper’s long-video claims.
(2) Limited ablations of key design choices. The quantizer comparisons and precision-budget sweep are useful, but they do not clearly separate the contributions of companding and dynamic precision allocation. For example, comparing with would show the benefit of companding, while using the same quantizer under fixed and dynamic precision would help isolate the benefit of the elastic policy. A sink-plus-recent window under the same memory budget would also test whether retaining distant low-precision history is a better use of memory. Without these controlled comparisons, it is difficult to determine which design choices drive the reported improvements over QVG.
Questions for authors
(1) Ablation of companding and dynamic precision allocation. Can you compare with , which disables companding while preserving truncation-exactness? Can you also compare fixed and dynamic precision allocation using the same quantizer under matched memory budgets? These experiments would clarify how much of the improvement comes from companding and how much comes from the elastic allocation policy.
(2) Long-video validation on text-only streaming models. Can you evaluate substantially longer rollouts, such as minute-long videos, on text-only streaming generation models such as LongLive or Rolling Forcing? Please report quality as a function of generation length, including after the cache reaches its budget and older chunks are heavily compressed or evicted. Additional action-conditioned world-model results would not resolve this concern: this evaluation should exclude action inputs so that the effect of KV compression can be assessed without action guidance. Please specify the frame rate, total generated frames, and history-window settings.
(3) Comparison with fixed-bit quantization and a sink-plus-recent sliding window. Can you compare Elastic-QVG with a baseline that directly quantizes the retained KV cache at a fixed bit-width and keeps only sink tokens and recent history, without progressively reducing the precision of older chunks? Please adjust the window size so that both methods use the same actual KV-memory budget, including metadata, and evaluate them on the same long-video workloads. This comparison would help determine whether the proposed progressive precision reduction preserves video quality better than a simpler combination of fixed-bit quantization and sliding-window eviction.