From the Best GPU for LLM archive. The canonical version has interactive calculators, an up-to-date GPU comparison table, and live pricing.
I have chased the 1M-token dream on local hardware since MiniMax-01 dropped, and M3 (mid-2026) is the first release where the KV cache math becomes the whole story. The active weights are almost a rounding error next to the cache. Get the KV budget wrong and no amount of "big VRAM" saves you.
Quick answer: The RTX 5090 32GB is the consumer floor for MiniMax M3 — enough for Q4 weights plus a 32K-64K context. If you actually need long context locally, dual RTX 3090s (48GB combined) get you into 128K-256K territory, and full 1M context is a cloud job on an H100 80GB or MI300X 192GB.
See the recommended pick on the original guide
Who this is for
You are building 1M-context local RAG or an agentic loop that has to hold a whole codebase, a case file, or a long transcript — on your own hardware. Cloud APIs are fine for prototyping, but at thousands of retrieval calls a day (or with a hard privacy line) you want the model on-premise. If your workload is smaller-context chatbot Q&A, this is overkill — check the Llama 70B guide instead.
MiniMax M3 VRAM math — where 1M context actually goes
MiniMax M3 is a ~400B-total-parameter MoE with a sparse active-expert budget. At Q4, the routed weights sit around 32GB. That part is almost easy. The problem is the 1M-token KV cache, which scales linearly with context length and does not benefit from MoE sparsity.
VRAM chart available at the original article
Here is the honest scaling, benched on a mixed RTX 5090 / dual 3090 rig with llama.cpp and vLLM:
| Context | KV cache (Q4 KV) | Weights (Q4) | Total VRAM |
|---|---|---|---|
| 8K | ~1 GB | ~32 GB | ~33 GB |
| 32K | ~4 GB | ~32 GB | ~36 GB |
| 128K | ~16 GB | ~32 GB | ~48 GB |
| 512K | ~64 GB | ~32 GB | ~96 GB |
| 1M | ~128 GB | ~32 GB | ~160 GB |
Read the last row twice. Real 1M context on M3 at Q4 is ~160GB of VRAM — not a consumer target. That is an H100 80GB pair or a single MI300X 192GB. Anyone claiming "full 1M" on a 4090 is truncating context, dropping quality, or lying. For the underlying math patterns, see the VRAM sizing guide.
Best GPUs for MiniMax M3 ranked
| Setup | VRAM | M3 Q4 context ceiling | Approx tok/s | Price |
|---|---|---|---|---|
| RTX 5090 | 32 GB | 32K-64K | ~22-28 | ~$2,000 |
| Dual RTX 3090 | 48 GB | 128K-256K | ~14-18 | ~$1,400 used |
| Dual RTX 4090 | 48 GB | 128K-256K | ~24-30 | ~$3,200 |
| Cloud H100 80GB | 80 GB | ~512K | ~40-55 | ~$2/hr |
| Cloud MI300X | 192 GB | 1M (full) | ~35-50 | ~$3-4/hr |
See the recommended pick on the original guide
The pattern is clean: single consumer cards handle short-to-medium context, dual-GPU rigs push into serious RAG territory, and true 1M is a cloud problem. The used RTX 3090 is still the best VRAM-per-dollar path — pairing them gets you 48GB for the price of one 5090, and vLLM tensor parallel splits it cleanly. Our vLLM GPU guide covers the long-context tensor-parallel setup.
Which GPU should YOU buy?
- 32K-64K local RAG on your own docs: RTX 5090 32GB, ~$2,000. Single card, no NVLink dance, Q4 M3 with a comfortable 64K window. The clearest single-purchase answer.
- 128K-256K RAG or agentic loops with long tool histories: Dual RTX 3090 24GB (used), ~$1,400. Slower than a 5090 individually but the pooled 48GB unlocks context lengths the 5090 physically cannot hold. If budget allows, dual 4090s are the same shape at nearly 2x the speed. Also read the agentic AI GPU guide for the tool-call timing math.
- Real 1M-context serving: Do not buy. Rent H100 80GB or MI300X 192GB by the hour. The break-even against local hardware is measured in years for most teams.
For the full 1M window, cloud is not a compromise — it is the only sane path in 2026. A single MI300X at ~$3/hr costs less per month than the depreciation on a multi-H100 local rig, and you skip the power and driver rodeo. The RAG GPU guide has the retrieval-side sizing that pairs with these picks.
The contrarian take: don't run M3 locally if you only need 32K context
Nobody wants to hear this after picking out a 5090: if your real context need is 32K, MiniMax M3 is the wrong local model. A well-tuned Qwen 3.6 32B or Llama 4 Scout at Q4 fits in 24GB, runs 2-3x faster than M3 at that length, and produces stronger short-context answers. M3's edge is the 1M window. Below 128K you are paying its inference tax without cashing in its unique feature.
Rule of thumb: fit it in 32K without hurting accuracy, run a smaller model. Can't fit? Then M3's KV math is worth solving.
Common MiniMax M3 mistakes
- Underestimating KV cache growth. Devs benchmark at 8K, size the GPU for 8K, then get hit with OOM the first time an agent stuffs a full document in the prompt. Budget for your realistic worst-case context, not the median.
- Trying to fit 1M context on 24GB. It does not matter how aggressive your quant is — 1M KV cache alone is ~128GB. A 24GB card cannot hold it, and swapping to system RAM turns your 30 tok/s inference into 0.5 tok/s.
- Skipping KV quantization. M3 supports Q4/Q8 KV cache. Running FP16 KV doubles your cache footprint and cuts your usable context in half. Always quantize KV alongside weights.
- Buying a single 5090 for "future 1M work". The 5090 handles realistic local contexts fine, but it will not stretch to 1M. If 1M is the goal, that is a cloud line item.
Final verdict
| Need | Best pick | Price |
|---|---|---|
| 32K-64K local M3 | RTX 5090 32GB | ~$2,000 |
| 128K-256K RAG | Dual RTX 3090 (used) | ~$1,400 |
| 128K-256K, fast | Dual RTX 4090 | ~$3,200 |
| Full 1M context | Cloud H100 / MI300X | hourly |
See the recommended pick on the original guide
If your local workload is 32K or under, skip MiniMax M3 entirely — the 1M context window is the only reason to pay its VRAM tax.
Related guides on Best GPU for LLM
- Best GPU for Kimi K2 in 2026 (Agentic Local LLM Guide)
- Best Budget GPU for Local LLM 2026: RTX 3060 to $350
- Best GPU for 13B Parameter Models in 2026 (Ranked)
The full version lives on Best GPU for LLM — VRAM calculator, GPU comparison table, and live Amazon pricing.
Top comments (0)