MiniMax H3 GPU benchmark calculator

Read the matrix without guessing

This page exists because there is no controlled single-GPU benchmark matrix for MiniMax H3 — not from MiniMax, not from ComfyUI, a gap called out publicly in August 2026. This ledger is the answer: every row names its GPU, its canvas, its frame count and its wall time.

The gap was stated in those words on X: "No controlled single-GPU benchmark matrix from MiniMax or ComfyUI" (@yume_arasaki, 2026-08-07). The follow-up question under every new clip is just as blunt — "Key question is how long did that 5s take" (@jikkujose, 2026-08-04). A MiniMax H3 GPU benchmark that does not state the canvas, the frame count, the step count and the acceleration stack cannot answer either one, which is why the calculator on this page asks for all four before it returns a number, and why every row of the ledger above repeats them.

Rows are hardware profiles

Each row names the card class and the environment that was actually used. The owned RTX 3060 row is a record, not a promise about every RTX 3060.

Columns are task tracks

Each column combines a model or precision track with a task. A measured cell links to its test_id; it is a projection of that run record.

Untested stays explicit

not tested means this site has not run the combination. It does not mean “unsupported,” “impossible,” or “will fail.”

No cross-row ranking

The rows do not share one machine, workflow, or memory budget. We place facts beside one another and do not calculate a speed ranking across them.

Every row carries its evidence grade

Every row also carries an evidence grade, and the grade is the first thing to read. Measured means this site ran it on its own bench and kept the record, failures included. Reported means a first-hand post stated the hardware and the result, and the row shows the handle and the date so the claim stays attached to whoever made it. Estimate means the engine extrapolated from an anchor because nobody has published that combination, and an estimate is never printed as if it had been measured. All 26 site rows share one environment line, printed once above the ledger instead of 26 times, so a difference between two rows is a difference in the workload and not in the machine.

What this bench measured

On this bench, at 1344×768 for 124 frames, the first formal run of each track came in at 2,581.8 s for REF2VA INT8 R2V with a peak of 11,649 MiB (94.8% of the card), 2,175.5 s for FL2VA T2V at 11,023 MiB (89.7%), 2,373.7 s for FL2VA I2V at 11,125 MiB (90.5%), and a median 528.6 s for the 4-step Turbo LoRA pass. That is what a MiniMax H3 GPU benchmark on an RTX 3060 comes to here: a 12GB consumer card that finishes all four tracks while sitting near the top of its memory, not a card with room to spare.

The 12GB row is site-measured on one owned bench. The 8GB row is a queued inventory item, not an inference from the 12GB measurements.

Three facts from this ledger

Each statement is tied to records above and carries its conditions. None is a cross-GPU ranking or a community-result verdict.

Workload scaling did not move VRAM much

In the R2V GPU 0 smoke-to-formal pair, the frame-pixel workload is approximately 40×. Peak VRAM moved from 11,591 to 11,649 MiB (+0.5%), while peak RAM moved from 43,176 to 43,587 MiB (+1.0%). The smoke was cold and the formal run warm, so this is an observation about this pair, not a scaling law.

Records: SITE-3060-R2V-GPU0-SMOKE and SITE-3060-R2V-GPU0-B1.

Cache Phase B telemetry stayed in a narrow VRAM band

The seven Phase B execution records, including the failed C5 telemetry record, span 11,163–11,773 MiB of recorded peak VRAM. C5 has no successful output, and C3/C8 have no Phase B performance record; the range is not evidence that all eight nodes work.

Records: PB-C1, PB-C2, PB-C4-RUN1, PB-C5 (failed), PB-C6, PB-C7.

R2V repeated output bytes matched

The two formal GPU 0 R2V runs each produced the same output SHA-256 prefix recorded in the cards: cc2a6f75…be6060f. Under this fixed seed, workflow and hardware setup, the outputs were byte-identical. The wall times remain 2,581.8 s and 2,579.8 s as separate observations.

Records: SITE-3060-R2V-GPU0-B1 and SITE-3060-R2V-GPU0-B1-RUN2.

Best GPU for MiniMax H3: VRAM class first, then the stack

This ledger measures one card, so it cannot hand you a winner, and the no cross-card ranking boundary below still holds. What the evidence does support is an order of operations.

VRAM class decides whether a run finishes at all, and the calculator reads the same bands the VRAM page publishes. Below 8,192 MiB there is no configuration this site can point at and call working. Between 8,192 and 12,287 MiB clips come out, but the reports that exist describe long cold runs rather than a setup you would work in. From 12,288 MiB up is the band this bench measured, and the measurement is tight rather than comfortable: 11,649 MiB peak on a 12,288 MiB card leaves 639 MiB, which is what ComfyUI left after filling the card, not headroom you can spend on a bigger canvas.

Inside one class the acceleration stack moves the number further than the model name on the box. On an RTX 4070 12GB the same full-HD five-second clip took 64 min 51 s on the base 20-step path, 14 min 33 s with LightX2V 4-step, and 5 min 0 s with Fast H3 VSA (@sep_is_heim, 2026-08-31) — a 12.97× spread on one card, wider than the 4.33× that separates the fastest and the slowest consumer card this site has a timing factor for at all. A faster stack can also raise the floor instead of lowering it: the Ref2VA VSA port goes out of memory on 12GB cards, so its bands start at 16,384 MiB. That is why the stack is an input and not a footnote, and why a number quoted without one is not a benchmark.

So the order is: pick the class that finishes, then the stack that clears your quality floor, then check the claim against a row that states your canvas, your frame count and your step count.

What makes a row a site benchmark

• Track: every row here is site_benchmark, not a community reproduction.
• Freeze: record the workflow revision and SHA-256, model files, input files, prompt, seed, canvas, frames, sampler, scheduler and audio state.
• Measure: report wall time, peak VRAM in MiB, peak system RAM, temperature, GPU binding and contamination before/after.
• Repeat: a formal site benchmark lasting at least 30 minutes runs twice; both test IDs and raw values remain visible. No average stands in for them.
• Retain failures: a failed execution or hardware incident is a record, not a footnote to delete.
• Separate tracks: smoke checks validate a chain; cache-node compatibility is not performance; rental hardware gets its own row; GPU 0 was used for the owned-bench heavy runs after the GPU 1 incident.

Full protocol: site-reproduction-protocol.md, version 0.2-draft.

Submitted benchmarks follow the same protocol through a review queue before they appear anywhere on this page. A submission that states its canvas, frames, steps and stack can be selected into the results below and carries its submitter's evidence grade; one that does not state them stays out, however interesting the number is. Review is also the only way the leaderboard gets longer — it is short because the qualifying rule is narrow, and loosening the rule is not on the table.

What is not here

No second-hand numbers in the matrix

Community reports remain community-reported. Their setup, timing and claims are not inserted into a site-measured cell.

No cross-card speed ranking

Different cards, environments and workflows cannot be reduced to one leaderboard. The 8GB row is not a support or failure verdict.

Turbo A/B stays on this 12GB card

The Turbo LoRA A/B ran once on this owned RTX 3060 12GB bench with the same prompt, seed, canvas, frames and workflow as the FL2VA T2V baseline, changing only the LoRA, steps and shift schedules. The same-environment pairing gives a 4.113×–4.132× wall-time range; it is not a cross-environment comparison and it is not placed beside any community "5×" claim. All three B-side runs peaked above 8,192 MiB, so this page makes no 8GB support or failure claim.

No averaged formal result

Repeat values are separate elements with separate IDs. If a future run changes, the raw ledger can show what changed.

No datacentre row to aim at

The fastest published H3 figure we know of is 5 s at 1344×768 in 1.653 s on eight B300 accelerators (@xieenze_jr, 2026-09-07). It stays out of the calculator's catalogue on purpose: it is context for what the model does when memory and interconnect stop mattering, not a target any consumer card is being measured against.

GPU benchmark questions

What MiniMax H3 GPU benchmarks were run on an RTX 3060 12GB?

The owned bench measured REF2VA R2V, FL2VA T2V, FL2VA I2V and a 4-step FL2VA Turbo LoRA workload at 1344×768 and 124 frames. The 26-record ledger includes formal runs, smoke checks, cache-node tests and retained failures rather than collapsing them into averages.

Can MiniMax H3 run on an RTX 3060 12GB?

Yes on this owned bench: R2V, T2V, I2V and the 4-step Turbo workload completed at 1344×768 and 124 frames. That is evidence for this machine and published software build, not a universal support promise for every RTX 3060 setup.

How much VRAM does MiniMax H3 use on an RTX 3060 12GB?

The measured 1344×768 base runs peaked at 10,863–11,649 MiB across the T2V, I2V and R2V raw observations. The R2V pair used 11,649 MiB, or 94.8% of the card, on both runs. Turbo peaks were 10,479, 10,895 and 11,185 MiB. These values apply only to the published conditions.

Can MiniMax H3 run on an 8GB GPU?

No conclusion is made here. The 8GB rental-class row is explicitly not tested, and a result on the owned RTX 3060 12GB bench is not an extrapolation to another card, memory size, precision or task.

How much faster was the MiniMax H3 4-step Turbo LoRA on the RTX 3060?

On one owned RTX 3060 12GB bench, the same FL2VA T2V workload with the 4-step Turbo LoRA took a median 528.6 seconds (range 526.7 to 528.9 seconds) against an A-side baseline of 2,175.5 and 2,176.2 seconds — a same-environment 4.113× to 4.132× wall-time range, not an average. All three Turbo runs peaked above 8,192 MiB VRAM, so the page makes no 8GB support or failure claim.