- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies the different roles of KV-cache positions in autoregressive video generation. Based on causal analysis, the authors propose AxisKV, which applies spatial compression to distant frames and quantization to recent frames. Experiments show that AxisKV reduces KV-cache memory while maintaining reasonable generation quality.
Critical strengths
The paper provides an interesting analysis of how different KV-cache positions affect video generation. The proposed method is simple and training-free, and achieves good memory compression with limited quality degradation on self-forcing.
Critical weaknesses
-
The proposed method mainly combines existing spatial pooling and quantization techniques based on temporal positions. Although the analysis provides some useful insights, the compression strategy itself is relatively simple and does not introduce new compression techniques.
-
The paper only reports calculated KV-cache memory reduction, without measuring actual peak GPU memory usage, inference latency, or FPS.
-
The generalization is not fully convincing. AxisKV shows noticeable quality degradation on CausVid, especially in aesthetic and imaging quality.
Questions for authors
-
Could the authors provide actual GPU memory usage and inference latency or FPS comparisons?
-
Why does AxisKV perform worse on CausVid? Can the authors explain when the proposed compression strategy may not work well?
-
Since all four evaluated models are based on Wan2.1, could the authors provide experiments on other video generation models with different backbones?
5 comments
W3/Q2: Performance Degradation on CausVid and Applicability
We agree that AxisKV exhibits noticeable quality degradation on CausVid. As discussed in Appendix F, independent pinned-state spatial-collapse probes reveal different compression sensitivities across generators. CausVid exhibits the largest semantic probe tax (−0.111), compared with Self-Forcing (−0.059), Rolling Forcing (−0.020), and LongLive (−0.018), consistent with its larger quality degradation under AxisKV. To further investigate this sensitivity, we conducted an additional pinned-state resolution ablation on CausVid, retaining 1, 28, or 104 spatial tokens per pinned state. Increasing the resolution from 1 to 104 tokens recovers only 17% of the aesthetic-quality loss and approximately 10% of the semantic-consistency loss, while all tested configurations remain substantially behind uniform 2-bit quantization.
AxisKV's fixed allocation is derived from causal interventions on Self-Forcing, while its application to other generators evaluates the transferability of this allocation. The CausVid results highlight the broader value of our causal probing approach: it characterizes position-dependent information requirements and helps identify generator-specific compression sensitivity. These findings can inform the design of model-specific compression allocations, rather than assuming that a fixed configuration is universally optimal.
We have further highlighted the role of causal probing in assessing model-dependent compression sensitivity in Section 4 and included the additional CausVid ablation in the revised Appendix F.
Q3: Generalization Beyond Wan2.1
We thank the reviewer for raising this important question. Our evaluation covers four representative autoregressive video generators, Self-Forcing, CausVid, Rolling Forcing, and LongLive, all based on Wan2.1. This backbone is also widely adopted in recent autoregressive video KV-cache management works, including Forcing-KV, Dummy Forcing, Deep Forcing, Relax Forcing, and Pyramid Forcing. We focus on this established setting to facilitate comparisons with existing methods and investigate how positional information requirements vary across generators under a shared backbone and cache architecture.
We acknowledge that generalization to different video generation backbones remains an open question. Extending AxisKV to other architectures would require examining their positional compression sensitivity and adapting the allocation accordingly, rather than directly transferring a fixed configuration. We view this as a meaningful direction for future work. We have clarified the Wan2.1-based scope of our evaluation in the revised Introduction.
Thank you for your detailed response. I think this is an interesting attempt, but there is still room for improvement. AxisKV reduces peak GPU memory usage by 8.8%, but the inference FPS drops from 14.72 to 8.90, which I don't think is an ideal trade-off.
Furthermore, the authors' explanation seems to be discussing a general property of autoregressive video generators, but additional CausVid experiments show that the proposed method does not generalize consistently across different generators. And the current experiments are all based on Wan2.1, without evaluation on newer backbones such as Wan2.2.
This doesn't change the fact that I think the motivation of this work is interesting. I hope the authors can propose a more effective or generalizable method based on the findings. However, I still lean towards rejection unless the authors can further address my concerns.
By the way, if the text in the figures could be selected and copied, it would greatly increase the readability of the paper.
We thank the reviewer for recognizing the value of our causal analysis, the simplicity of AxisKV, and its memory compression effectiveness. We address the concerns below with additional system-level measurements and clarification of our contributions and limitations. Changes in the revised manuscript are highlighted in blue for ease of reference.
W1: Novelty of the Compression Strategy
We agree that the spatial pooling and quantization operators used in AxisKV are not themselves new. This is an intentional design choice, as stated in Introduction. Our contribution lies in identifying position-dependent information requirements through causal analysis and translating these findings into position-specific compression-axis selection**, rather than proposing new compression operators.
Specifically, our persistent, position-matched interventions reveal two key findings:
These findings directly motivate AxisKV's allocation. Furthermore, under the same 8× historical KV payload budget and implementation, uniform pooling and uniform quantization degrade all three primary consistency dimensions, whereas AxisKV shows no statistically significant differences from the uncompressed baseline on these dimensions.
The novelty is therefore the causal and experimental connection between positional information requirements and compression-axis selection. Using established compression operators allows us to isolate the contribution of the allocation itself without introducing additional factors.
W2/Q1: Actual GPU Memory Usage, Latency, and FPS
We thank the reviewer for emphasizing the importance of system-level measurements. To address this concern, we additionally implemented write-time compressed KV storage and measured GPU memory usage, generation latency, and FPS on a single GH200 GPU. Unlike the read-time compression used for controlled quality analysis in the original paper, this implementation physically stores historical KV states in compressed form.
For the nominal 12× AxisKV configuration, we obtain:
Actual historical KV storage is reduced by 9.54×, closely matching the approximately 9.6× reduction predicted in Appendix J after accounting for metadata. End-to-end peak GPU memory decreases by approximately 2.1 GiB (8.8%). The smaller reduction in peak memory is expected because model weights, activations, and other buffers are not compressed alongside the historical KV cache.
This memory saving comes with additional inference overhead: generation time increases from 32.4 s to 53.6 s. The current implementation reconstructs compressed KV states during reading while retaining the original attention sequence length. Thus, AxisKV provides a memory–latency trade-off rather than inference acceleration.
We have added a brief summary of these system-level results in Section 4 and included the detailed GPU memory, latency, and FPS measurements, along with implementation details and limitations, in the revised Appendix J.