- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper looks at how to speed up diffusion models by skipping some Transformer evaluations and reconstructing the missing outputs. MoorCache uses past evaluations to predict part of the current output, then adds information from a current observation to recover what the history missed. The observation comes from different sources depending on the model: for Wan2.1 and DiT, it uses the conditional branch; for HunyuanVideo and FLUX, it runs a lower-resolution pass. It uses fixed schedules and does not require training. Experiments cover four model families. The results suggest that adding the current observation can improve quality at a given compute budget, and the paper reports both FLOPs and measured latency.
Critical strengths
1、The paper separates two possible sources of reconstruction error: choosing the wrong amount of movement along the historical direction, and missing a direction that history cannot represent. The multi-secant analysis helps test whether simply using more history solves the problem.
2、The same-cost ablation is useful. Keeping the observation computation but removing its contribution lowers PSNR on Wan2.1, HunyuanVideo, and FLUX, which gives evidence that the way the observation is used matters.
3、The evaluation covers video, text-to-image, and class-conditional generation. It also reports measured H100 latency and includes the observation and reconstruction costs.
Critical weaknesses
1、The headline comparison is tied to one CFG setting. The paper highlights that historical input directions capture 98.9% of input movement, while historical residual directions capture only 2.7% of the deployed residual movement. But the 2.7% result is for the CFG-combined residual at a particular guidance weight. Appendix D reports much higher coverage for a single residual branch and for intermediate features, and shows that coverage changes substantially with the guidance weight. This is an interesting result for that setup, but it does not support a broad claim about diffusion caching in general.
2、The comparison with other methods that use current-step information is incomplete. The paper discusses FasterCache and RFC, but does not compare against them in the main benchmark. Since the proposed contribution is how current information is added to the historical prediction, a same-cost comparison with these methods would help show what MoorCache adds.
3、The fixed settings need more justification. The method uses the same observation gain across its different model-specific setups, but the paper gives little evidence that this choice works reliably across backbones. It also does not show how results change with the lower-resolution proxy settings. .
Questions for authors
1、Is the 2.7% coverage result specific to the CFG-combined residual at the reported guidance weight? How should it be interpreted alongside the much higher single-branch and intermediate-feature results?
2、Did the authors test whether the fixed observation gain and lower-resolution proxy settings work across the different backbones?
3、Can the authors clarify why FasterCache and RFC are not directly comparable, or provide existing same-cost results against them?
2 comments
The experiments have adressed most concers.
The added experiments in the rebuttal have adressed most of my concerns, it is suggested to include them in the final version.
We thank the reviewer; all three questions concern the scope of a claim, and the corresponding sweeps have been added.
Q1 — scope of 2.7%. 2.72% applies only to "the CFG-combined residual of the sampler update", the least favourable end of the guidance sweep; the deployed objective on Wan2.1 is the single unconditional branch at 64.8% — different objects, an order of magnitude apart. Abstract and §3.3 will restrict the headline figure and state both side by side. The cause is structural (App. D): both branches share the latent and timestep and are strongly aligned, so at w = 5 the combined displacement is dominated by amplified cross-branch gap motion (coverage 1.3–9.7%), nearly orthogonal to its historical secant. Table D1 entries are read side by side, not substitutable.
What we keep is w-independent and a criterion: measure C on the deployed objective (64.8%); when C is too low for the historical secant to explain the target displacement, current observation must be introduced — a necessary condition, not a design preference. Expanding the basis from one secant to eight with offline least-squares coefficients recovers only 3.49% of the missed directional energy (median), so more history does not solve it. Together they give Eq. (13), an identity but not a tautology: conditions (acute angle; non-increasing norm) that are true or false on recorded proxy data at every w, and will move from App. D to §3.5 as a decision rule. End-to-end PSNR against the strongest equal-latency baseline rises monotonically, +0.74 dB at w = 1 to +3.00 dB at w = 10 (Table D2).
Table D1. Coverage by object. 2.72% = event-level median (2.7% in abstract). At w = 1 the residual equals the conditional-branch residual, so 68.87% matches App. D's 68.9%; recombined diagnostics 65.6 / 1.63 / 0.75% at w = 1 / 5 / 7.5.
Table D2. PSNR vs the strongest equal-latency baseline (SeaCache).
Q2 — generality of β and proxy resolution. Both are now sweeps. β is optimal at 1.0 on all four backbones, moving only 0.17 / 0.32 / 0.14 dB over 0.75–1.25, so one value suffices; the oracle β exceeds the chosen point everywhere (Table D3). Resolution saturates at 1/4: 1/2 buys only 0.21 dB (HunyuanVideo) and 0.26 dB (FLUX) at 4.0× the added FLOPs, and the 1/4 cost matches the main table (10587.4 T and 1241.2 T). On FLUX, all dual-stream 31.94 dB, first eight 31.62 dB, dual-stream plus all single-stream (ours) 32.12 dB — 0.18 dB above dual-stream alone, so observation depth is part of the method.
Table D3. β sweep (1.0 adopted).
Table D4. Proxy-resolution sweep, abscissa in added FLOPs.
Table D5. FLUX.1-dev, blocks observed by the proxy.
Q3 — comparability with FasterCache and RFC. We consider them comparable, compare both at equal measured latency, and will remove the related-work sentence implying otherwise. Table D6 gives FasterCache's three configurations against ours at aligned latency, Table D7 ResCa on three backbones; RFC gives 31.72 dB @ 2.44×, a +2.30 dB margin for us. Leads are +1.60 dB over CFG-gap reuse and +1.07 dB over the strongest baseline. Table 12 fixes the CFG treatment to isolate the reconstruction rule and cannot substitute for this comparison; the revision will say so.
Table D6. FasterCache, Wan2.1, latency-aligned.
Table D7. ResCa, official implementation.