- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
MetricKV studies the numerical compression of historical visual KV states in streaming video understanding. The implementation combines Layer-RMS normalization with progressive RVQ. Fixed-readout experiments report 64× dynamic-KV compression with scores of 69.04 versus 69.94 FP16 on OVO-Bench and 79.10 versus 80.74 on the evaluated StreamingBench subset. Additional experiments cover another backbone, transfer of Layer-RMS to KVTC, and integration with streaming memory policies.
Critical strengths
- A clear and reusable codec design framework. The exact distortion decomposition explains which latent metric should accompany a decoder. Transferring Layer-RMS to KVTC without replacing its scalar coder provides empirical support that the reconstruction objective is an independently useful design choice.
- Strong dynamic compression under controlled evidence selection. The fixed-readout protocol holds the selected frames and token budget constant, helping isolate representation quality. Retaining approximately 98% of reference scores at 64× dynamic compression, with a second-backbone evaluation and a progressive index stream, is potentially valuable for long-lived visual memory.
Critical weaknesses
-
Practical overhead is not adequately evaluated. Table 4 reports 0.467 s encoding and 0.027 s decoding per frame at 64× compression, but lacks runtime comparisons with the same uncompressed system. End-to-end ingestion throughput and QA latency should be evaluated to determine whether compression benefits outweigh its computational overhead, especially for bounded histories.
-
The novelty is insufficiently demonstrated. The theoretical derivation largely builds on classical weighted least squares and PCA, with related ideas already explored in KVTC.
Questions for authors
- End-to-end system evaluation: Can the authors compare ReKV or SimpleStream with and without MetricKV under identical hardware, inputs, retrieval policies, and cache configurations? Reporting ingestion throughput, QA latency, and total memory usage would help clarify whether compression benefits outweigh the additional codec overhead.