- Rating
- 2
- Confidence
- 4(+2)
- Informativeness
- 1(−1)
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper proposes ClipStore which enables exact feature reuse when encoding overlapping video clips for latent-cache construction. It identifies reusable regions from temporal support and phase, combines shallow and deep cached features, and preserves request-local encoder state. A request plan determines which features are retained. Experiments on Wan2.1 check output equality, complete construction cost, and the effects of different request structures.
Critical strengths
The paper addresses a useful problem that reusing computation across overlapping clips while preserving the outputs of independent encoding. The timing includes feature construction and final writes, and the authors report cases where reuse does not help. This makes the comparison more credible within the tested setting.
Critical weaknesses
-
The design's contribution and generality remain limited. Propositions 1–2 establish correctness and read-set sufficiency, but do not explain how to choose reuse depths for another encoder. The experiments mainly compare two selected cuts with those same cuts used separately in one Wan encoder, leaving other feasible cuts and simpler budget-based choices untested. On the reference plan, the added time saving over the faster fixed cut is 9.93%; the 21.9% payload reduction corresponds to only 3.21% lower total GPU peak. These are valid local gains, but without cut-selection and transfer evidence, their broader significance is not convincing.
-
The presentation is poor and overly dense, making the reuse procedure hard to follow. The full executor is deferred to Appendix B. A clearer worked example should connect the boundary calculation, A/B switching, and retained features for one complete request.
Questions for authors
- Can you give a worked request that connects raw-frame offsets, feature indices, phase matching, and the A/B switching points?
- Can you replay requests from the intended workflow after sampling, crop, and augmentation constraints, and report compatible-group sizes and complete construction costs?
- How were cuts A and B selected? How do other feasible cuts or a simple budget-based choice compare, and what must be changed and revalidated for another encoder or precision?