MiniMax M2.7 needs ~159.1 GB VRAM. NVIDIA H200 141GB has 141.0 GB. With UD-IQ4_XS quantization, expect ~65 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
349.3 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
5.8 tok/s
TTFT
33188 ms
Safe context
4K
Memory
490.3 GB / 141.0 GB
Offload
70%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly 15.9 GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Very compromised (needs ~14.5 GB host RAM) | 66.6 tok/s | 1587 ms | 4K |
| Coding | A | Very compromised (needs ~15.9 GB host RAM) | 65.2 tok/s | 2967 ms | 4K |
| Agentic Coding | A | Very compromised (needs ~18.8 GB host RAM) | 62.8 tok/s | 4486 ms | 4K |
| Reasoning | A | Very compromised (needs ~15.9 GB host RAM) | 65.2 tok/s | 3507 ms | 4K |
| RAG | A | Very compromised (needs ~18.8 GB host RAM) | 62.8 tok/s | 5608 ms | 4K |
How MiniMax M2.7 (230B params) fits at each quantization level on NVIDIA H200 141GB (141.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_KBest for your GPU | 2 | 89.7 GB | Low | A84 |
Q3_K_S | 3 | 112.7 GB | Low | F0 |
NVFP4 | 4 | 128.8 GB | Medium | F0 |
Q4_K_M | 4 | 140.3 GB | Medium | F0 |
Q5_K_M | 5 | 165.6 GB | High | F0 |
Q6_K | 6 | 188.6 GB | High | F0 |
Q8_0 | 8 | 246.1 GB | Very High | F0 |
F16 | 16 | 471.5 GB | Maximum | F0 |
Copy-paste commands to run MiniMax M2.7 on your machine.
Run
lms load MiniMax-M2.7 && lms server startYour hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 235B | A | 56.1 tok/s |
Yes, NVIDIA H200 141GB can run MiniMax M2.7 with a A grade (Very compromised (needs ~15.9 GB host RAM)). Expected decode speed: 65.2 tok/s.
MiniMax M2.7 (230B parameters) requires approximately 159.1 GB of memory with UD-IQ4_XS quantization.
The recommended quantization for MiniMax M2.7 is UD-IQ4_XS, which balances quality and memory efficiency.
On NVIDIA H200 141GB, MiniMax M2.7 achieves approximately 65.2 tokens per second decode speed with a time-to-first-token of 2967ms using UD-IQ4_XS quantization.
For coding workloads, MiniMax M2.7 on NVIDIA H200 141GB receives a A grade with 65.2 tok/s and 4K context.
On NVIDIA H200 141GB, MiniMax M2.7 can safely use up to 4K tokens of context. The model's official context limit is 205K, but available memory constrains the safe maximum.
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/minimax-m2-7-on-h200-141gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: