ComfyUI-MiniMaxH3-CLIPCached: Disk Cache for H3 Conditioning

ComfyUI Wikinews

A new ComfyUI node caches MiniMax H3 Qwen3-VL conditioning to disk: repeat runs with the same prompt skip the 14.6 GB encoder, dropping conditioning from 29.9 s to 1.1 s.

ComfyUI-MiniMaxH3-CLIPCached (GitHub) is a new MIT-licensed node pack that caches MiniMax H3 text/vision conditioning to disk. Repeated generations with the same prompt and reference inputs skip the Qwen3-VL encoder entirely: the conditioning stage drops from about 30 seconds to about 1 second, and the 14.6 GB encoder never gets loaded.
CLIPCached workflow with the cached node in place

The cached node replaces the stock H3 conditioning node; the diffusion stage is untouched.

What it caches, and what it does not

This is not a sampling accelerator. It is not TeaCache or FirstBlockCache, and it does not touch sampling steps. The node replaces ComfyUI's stock H3 conditioning node: on a cache hit it loads previously computed text/vision conditioning from disk instead of running the Qwen3-VL encoder, and the diffusion stage proceeds unchanged.

ChangeNew cache entry?
Prompt textYes
Encoder checkpointYes
Keyframe/reference pixels visible to the encoderYes, when encoder-visible content changes
Seed, sampler, scheduler, stepsNo
Downstream LoRA or strengthNo

That split matters for iterative workflows: if you rerun the same prompt tweaking only sampler settings or LoRA weights, every run after the first is a hit.

Measured numbers

The author's controlled benchmark (5 cases per mode, medians, RTX 5080 16 GB under WSL2, deliberately cold encoder reads for native and miss):

ModeConditioningPeak VRAMPeak process RAM
Native29.85 s15.24 GiB29.25 GiB
Cache MISS32.23 s15.24 GiB28.25 GiB
Cache HIT1.12 s2.67 GiB3.38 GiB

A miss is intentionally not a fast path: it still runs the encoder and writes the result to disk, costing about 2 extra seconds. But after the encode the encoder is unloaded instead of staying resident, so sampling runs with that memory freed. In the author's screenshot, native keeps both the 11.7 GB H3 model and the 14.6 GB encoder resident while sampling, while a cache hit leaves only the DiT loaded and process RAM drops from 40 GB to 25.5 GB.

Nodes and cache management

The pack includes cached counterparts of the stock H3 Image-to-Video (FL2VA) and Reference-to-Video (Ref2VA) nodes, plus dual-resolution variants that prepare conditioning for both the base pass and an upscale target, and a shared encoder-name selector.

Every unique conditioning request becomes a cache entry that persists until deleted, and they add up if you iterate a lot. A built-in cache manager panel handles browsing, tagging and pruning entries. Requirements are ComfyUI 0.30.0 or newer with the native H3 nodes.

Availability

The node is in ComfyUI Manager and the registry as minimaxh3-clipcached, or clone the repository into custom_nodes. The current version has no automatic cache eviction, Ref2VA uses fixed reference slots, and GGUF encoders are untested.

Comments

Sign in with GitHub to join the discussion.

Loading comments…
ComfyUI-MiniMaxH3-CLIPCached: Disk Cache for H3 Conditioning | ComfyUI Wiki