Guides

MiniMax H3 in ComfyUI: Change Your Nodes Before You Buy VRAM

In ComfyUI, MiniMax H3 cards from 8 to 32 GB hit a 10x slowdown at about the same clip size. Memory nodes move it further, so change nodes before you buy VRAM.

MesmerTools•November 12, 2026•4 min

Someone on r/StableDiffusion posted their first scene made with MiniMax H3, the open video model, rendered in ComfyUI on an RTX 3090. It's a Godzilla scene that took about ten minutes per 7-second shot at 720p. It got 3,000 upvotes, and the obvious next question is whether the model fits on your card.

That's the wrong question. People run H3 on 6 GB, slowly. What matters is where your setup hits a wall, the point where a little more video makes a render ten times slower. In the runs I lined up, cards from 8 to 32 GB fell off at about the same clip size, and memory nodes carried two cards far past it. So I'd change my nodes before I bought a card.

A small graphics card fed by a tall rack of fifty glowing layer slabs over a bridge of light, beside the headline Will it fit? Wrong question

In ComfyUI, MiniMax H3's weights are the cheap part

ComfyUI keeps what fits in VRAM and copies in the rest as each of H3's 50 blocks comes up. With the weights in system RAM, all 21 GB reach the card in a second or two. The math takes far longer, because each weight has to meet every token, the patches H3 cuts your video into. Here's one step on a 12 GB card.

Moving every weight is a sliver next to a 14-second step on a 12 GB card, and the proportions flip when those weights generate one LLM token at a time.

So speed follows the clip. Tokens come to about 7,000 × megapixels × seconds. Most layers scale with that, and attention, where every token looks at every other, scales with its square. Picture your clip as a brick of tokens.

Estimates from H3's published architecture: the square outgrows the brick as the clip gets longer, and near the end sparse attention punches holes in it on one 5090 run, cutting the cost and some of the quality.

That gives you a test. Doubling the seconds should about triple the time per step, and an 8 GB laptop measured 2.8x. If you see 10x, you've crossed a wall.

But past a certain size, cards from 8 to 32 GB all fall off

One RTX 5090 owner rendered the same 15 seconds of video at three sizes, and the times only make sense once you can see the memory.

40% more pixels costs 11x the time once working memory crosses the brim, then attention gets poured in head groups and an even bigger clip finishes in about a fifth of that time.

On Windows, the driver moves that overflow into system memory and the run carries on, every read crossing the bus. So a bigger card should push the wall out. I put the three clearest reports on one token scale, and it barely does.

Three very different tanks trip in the same narrow band, then one switch sends the 32 GB card past it and another sends a different 16 GB card past that.

All three sit between about 56,000 and 78,000 tokens, across 4x the VRAM. I can't explain that: the laptop runs out of system RAM, the stacks differ, and three reports can be coincidence. The two runs that got past it are what I'd act on.

So move the wall with nodes before you buy VRAM

The 5090 owner added two nodes from KJNodes, a popular ComfyUI pack, MiniMaxLowVRAMAttention and MiniMaxChunkFeedForward. They work through attention heads and tokens in small groups, and the answer comes out the same.

The second used SelfLift-Fish, another set of nodes, which took a 16 GB RTX 5070 Ti to 220,000 tokens. By default it keeps just 4 GiB of weights in VRAM. Weights are cheap to move, so the room goes to working memory. That run also used sparse attention, which skips most token comparisons, and only its last 4 of 10 steps ran at full size.

So I'd start with chunking. I'd raise the clip until doubling it costs far more than triple, and add those two nodes there, before I tried a smaller clip or a bigger card. As of November 2026, three reports is all I've got, so I don't know whether your wall lands in the same band.

More from the Blog