DiCache: Adaptive Diffusion Caching
- DiCache is a training-free, runtime-adaptive caching strategy that uses shallow-layer features to decide when to compute or reuse cached information in diffusion models.
- It employs an online probe profiling scheme to measure shallow residual differences, triggering full recomputation when the accumulated error exceeds a preset threshold.
- Dynamic Cache Trajectory Alignment accurately interpolates between cached states, achieving speedups up to 3.22× while maintaining high output fidelity.
DiCache is a training-free, runtime-adaptive caching strategy for accelerating diffusion transformer models for image and video generation. In its canonical usage, the term refers to the method introduced in “DiCache: Let Diffusion Model Determine Its Own Cache,” which answers both “when to cache” and “how to use cache” by using the model’s own shallow-layer features to drive online cache scheduling and multi-step cache combination, rather than relying on predefined empirical laws or dataset-level priors (Bu et al., 24 Aug 2025).
1. Background and lineage
DiCache belongs to a broader line of inference-time acceleration methods that exploit temporal redundancy in diffusion sampling. Earlier work such as DeepCache showed that adjacent denoising steps exhibit significant temporal similarity in high-level features and proposed caching and reusing high-level U-Net features while recomputing low-level features, yielding a speedup factor of for Stable Diffusion v1.5 with only a $0.05$ decline in CLIP Score, and for LDM-4-G with a slight decrease of $0.22$ in FID on ImageNet (Ma et al., 2023).
The specific motivation for DiCache arises from two recurring design questions in diffusion caching: when to reuse cached computation and how to reconstruct the current step from previously cached states. The DiCache paper argues that prior methods typically answer these questions with static or offline heuristics, including fixed caching intervals, dataset-calibrated schedules, or handcrafted rules for combining multi-step caches, and that such rules can fail on outlier samples because diffusion dynamics are highly sample-dependent (Bu et al., 24 Aug 2025).
This places DiCache in the training-free adaptive branch of diffusion caching. Later literature explicitly treats it as a state-of-the-art dynamic, training-free caching scheme alongside TeaCache and EasyCache for video diffusion transformers, while also distinguishing its scheduling logic from its cache-usage mechanism (Agrawal et al., 14 Jul 2026).
2. Formal setting and motivating observations
The method is developed for flow-matching or rectified-flow diffusion transformers. For timestep , latent input , condition , and transformer blocks , the intermediate representation after block is
with full-model output $0.05$0. DiCache uses residuals
$0.05$1
and in particular the full residual $0.05$2 (Bu et al., 24 Aug 2025).
Two empirical observations motivate the design. First, the relative L1 difference between shallow-layer features at adjacent timesteps tracks the relative L1 difference between final outputs. The paper defines the probe-based estimate
$0.05$3
for a shallow probe depth $0.05$4, and reports that the Spearman correlation between shallow-layer differences and full-output differences is approximately $0.05$5 already for $0.05$6. By contrast, raw input differences $0.05$7 are described as mostly monotonic and not useful as a cache-error proxy (Bu et al., 24 Aug 2025).
Second, residual trajectories across layers are similar. The residual sequences $0.05$8 and $0.05$9 evolve with similar trends in feature space, which suggests that shallow residual trajectories can guide interpolation between cached full residuals. This observation underpins DiCache’s second component, Dynamic Cache Trajectory Alignment (Bu et al., 24 Aug 2025).
3. Online Probe Profiling Scheme
The first principal component of DiCache is the Online Probe Profiling Scheme, which addresses when to cache. At every timestep, the method runs only the first 0 blocks as a shallow probe,
1
with probe residual 2. The estimated cache error between adjacent steps is then accumulated into a running sum 3. Cache reuse continues while the accumulated estimate stays below a threshold 4; once the threshold is exceeded, the method triggers a full recomputation, refreshes the cache, and resets the accumulator (Bu et al., 24 Aug 2025).
Operationally, the first timestep uses a full forward pass and stores a full residual 5. At later timesteps, DiCache first computes the shallow probe. If 6, it skips the deeper blocks and reuses the cached residual via 7. Otherwise it resumes full computation from block 8 onward, computes a new full residual, and resets the schedule. Because recomputation resumes from the already computed probe state, the shallow pass is not discarded (Bu et al., 24 Aug 2025).
This scheduling rule is fully training-free. It introduces no new learned parameters and depends only on the probe depth 9, the reuse threshold $0.22$0, and inexpensive relative L1 calculations on shallow features. In the reported experiments, $0.22$1 is used for WAN 2.1, HunyuanVideo, and Flux, reflecting the claim that even the first block provides a sufficiently informative runtime sensor (Bu et al., 24 Aug 2025).
4. Dynamic Cache Trajectory Alignment
The second principal component, Dynamic Cache Trajectory Alignment, addresses how to use cache. A simple reuse rule would approximate the current full residual by the most recent cached residual. DiCache instead retains the two most recent full residual caches, $0.22$2 and $0.22$3, and uses the shallow probe trajectory to estimate where the current step lies between them (Bu et al., 24 Aug 2025).
The full residual is modeled as approximately linear between the two cached points,
$0.22$4
and the scalar position $0.22$5 is estimated from shallow residuals. With probe residuals $0.22$6, $0.22$7, and $0.22$8, the paper defines
$0.22$9
This produces the DCTA approximation
0
The output is then reconstructed as 1 (Bu et al., 24 Aug 2025).
The significance of this construction is that both scheduling and cache usage are driven by the same shallow probe. Online Probe Profiling uses shallow-layer feature differences to decide whether to recompute, while DCTA uses shallow residual trajectories to align multi-step caches. This yields a unified framework in which the model, in the paper’s phrasing, determines its own cache (Bu et al., 24 Aug 2025).
5. Empirical performance, limitations, and later developments
DiCache is evaluated on WAN 2.1-1.3B, HunyuanVideo, and Flux.1.0-dev on an NVIDIA A800 80GB GPU, using LPIPS, SSIM, and PSNR against vanilla outputs as the primary fidelity metrics. The reported results show that DiCache improves both speed and fidelity relative to several accelerated baselines, including TeaCache, EasyCache, TaylorSeer, and naive reduced-step baselines (Bu et al., 24 Aug 2025).
| Model | DiCache speedup | Reported fidelity |
|---|---|---|
| WAN 2.1 | 2 | LPIPS 3, SSIM 4, PSNR 5 |
| HunyuanVideo | 6 | LPIPS 7, SSIM 8, PSNR 9 |
| Flux | 0 | LPIPS 1, SSIM 2, PSNR 3 |
Ablations show the expected trade-off between probe cost and fidelity. On HunyuanVideo, increasing probe depth from 4 to 5 improves LPIPS from 6 to 7 and PSNR from 8 to 9, while reducing speedup from 0 to 1. The reuse threshold 2 plays the usual quality-efficiency role: for HunyuanVideo, 3 yields LPIPS 4 and speedup 5, whereas 6 yields LPIPS 7 and speedup 8 (Bu et al., 24 Aug 2025).
Subsequent work treats DiCache as an important reference point. ACID characterizes DiCache as using a feature-level drift proxy from a shallow probe and adds a training-free dual-threshold wrapper that switches between 9 and 0 based on the rate of change of the existing drift signal. For HunyuanVideo with DiCache, ACID reports latency 1 s and speedup 2 with PSNR 3, SSIM 4, and LPIPS 5, compared with a fixed low-threshold DiCache configuration at 6 s and 7 speedup (Agrawal et al., 14 Jul 2026).
ReCache separates DiCache into two parts: Dynamic Cache Trajectory Alignment as the cache mechanism and Online Probe Profiling as the scheduler. It then replaces the scheduler with a budget-aware REINFORCE policy. On FLUX.1-dev with a 8-step budget, “ReCache DiCache” keeps the same TFLOPs and speedup as DiCache, 9 TFLOPs and 0, while reducing LPIPS from 1 to 2 and increasing HPS from 3 to 4 (Aliev et al., 4 Jun 2026).
Adjacent work has also generalized or critiqued DiCache-style ideas. Q&C studies the interaction between post-training quantization and DiCache-style caching in diffusion transformers and shows that naive combination can cause catastrophic degradation unless calibration and exposure-bias issues are corrected with TAP and VC (Ding et al., 4 Mar 2025). SpectralCache argues that DiT denoising is non-uniform across timestep, depth, and feature dimensions, and proposes TADS, CEB, and FDC as a richer decision framework than a single global threshold (Li, 5 Mar 2026). These developments suggest that DiCache established a useful baseline formulation, but not the endpoint of adaptive diffusion caching.
6. Other uses of the name
The label “DiCache” is not unique to diffusion-model caching. In LLM systems, the term is also used for disk-based key-value cache designs in retrieval-augmented generation. “Shared Disk KV Cache Management for Efficient Multi-Instance Inference in RAG-Powered LLMs” describes a “DiCache” or “RAG-DCache / Shared RAG-DCache” design that stores per-layer key/value tensors for retrieved documents on NVMe SSD, shares them across instances, and reports a 5–6 increase in throughput and a 7–8 reduction in latency depending on configuration (Lee et al., 16 Apr 2025).
A separate line of work, “LLM-dCache,” uses GPT-driven localized data caching for tool-augmented LLMs by exposing cache operations as callable tools and allowing the model to manage cache decisions via prompting. On an industry-scale geospatial platform, it reports an average 9 improvement in Copilot times across models and prompting techniques (Singh et al., 2024).
In networking, the related acronym DAC denotes “D2D-Aware Caching” in mmWave cellular networks, where cacheable content is split into two groups to facilitate device-to-device exchange. That work is analytically unrelated to diffusion-model DiCache, but it illustrates that the name has appeared in multiple caching literatures with distinct meanings (Giatsoglou et al., 2017).