- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
TRAC is a training-free framework for accelerating AR video generation. The main idea is to make cache reuse across denoising steps more aware of the generation trajectory. TRAC combines an offline schedule search for cache reuse, CFG residual reuse across denoising steps, and a structural correction mechanism to reduce computation while limiting error accumulation across autoregressive chunks. Experiments on two video generation models show that TRAC can achieve speedups with relatively small quality degradation.
Critical strengths
1. TRAC achieves speedups while keeping the quality degradation relatively small. For example, it achieves around 6× speedup on SkyReels-V2 with only a small drop in VBench.
2. The idea of using different reuse patterns for different denoising steps is reasonable, and RCS, ATGS, and SSC work together in a fairly coherent way. The ablation studies also make it relatively easy to see what each component contributes.
Critical weaknesses
1. I am not convinced that the main ideas are sufficiently novel. RCS, CFG residual reuse, and structural correction all seem closely related to existing ideas in cache reuse, adaptive scheduling, and error correction. Overall, the method feels more like combining and adapting existing techniques to AR video generation.
2. TRAC requires an offline calibration stage to determine the reuse schedule, but it is not clear whether or how this cost is accounted for in the reported speedups. Since the baselines do not appear to require the same offline schedule search, I think the paper should report the calibration cost and explain how it should be accounted for in the evaluation.
Questions for authors
-
I would appreciate more clarification on the novelty of the proposed approach. In particular, it would be helpful if the authors could more clearly explain what the key new insights are behind RCS, CFG residual reuse, and structural correction, and how they differ from existing approaches to cache reuse, adaptive scheduling, and error correction.
-
TRAC requires an offline calibration stage to determine the reuse schedule, but the cost of this stage is not clearly reported in the paper or reflected in the reported speedups. Since the baselines do not appear to require a similar offline schedule search, it would be helpful to provide more details on the calibration cost, such as the required computation, time, number of calibration samples, and model evaluations. It would also be helpful to clarify whether this cost is excluded from the reported latency and how it would be amortized in a practical setting.