- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper investigates feature-caching-based acceleration of the denoising process in diffusion-based 3D generative models. Exploiting the consistency of residual prediction reliability across inputs, it uses offline analysis to identify computations that can be replaced by prediction. Periodic exact refreshes provide historical residuals for extrapolation, reducing computation and achieving substantial target-stage speedups while largely preserving generation fidelity.
Critical strengths
The paper establishes a reasonably coherent link between its analysis, method, and experimental validation. For example, the depth-permutation ablation preserves the prediction budget while changing prediction locations, providing targeted evidence for the usefulness of reliability-aware placement.
Critical weaknesses
The incremental contribution over closely related methods (e.g., ERTACache) remains unclear. Further clarification or experimental evidence is needed to assess the novelty; please see the questions below for details.
Questions for authors
- Could the authors clarify the standalone contribution of RRP relative to prior offline error-profiling methods, such as SmoothCache and ERTACache, independently of GAR and EAR?
- Could the authors explain Table 3 in more detail and clarify the advantage of GAR over simpler submodule-level caching or forecasting methods, such as FORA, SmoothCache, and TaylorSeer? In particular, what do “Cells” and “Units” represent, how do the Submodule and Mixed settings differ in execution, and why does Mixed achieve a higher speedup despite having the same number of prediction cells?
- The experiments compare R3D with TeaCache and SmoothCache, but do not include a forecasting-based baseline such as TaylorSeer. Could the authors provide such a comparison under comparable speed–quality settings, or explain any adaptation barriers? This would help distinguish the benefits of residual forecasting itself from those of the proposed reliability routing.
- Could the authors clarify how much of the speedup in Table 1 is attributable to R3D itself versus the additional exact caching optimizations described in Appendix C.4? Were equivalent optimizations enabled for the baselines? A breakdown on one representative backbone would help connect the controlled ablations to the main deployment results.