MiniCPM-V-4.7-35B-A3B-CRACK requirements — can you run it?
~35.0B parameters · 3 quantizations measured · updated 2026-10-14 · source: dealignai/MiniCPM-V-4.7-35B-A3B-CRACK-GGUF
MiniCPM-V-4.7-35B-A3B-CRACK is a mixture-of-experts model (~35B total, ~3B active per token) (34k downloads on Hugging Face), published as GGUF by the community. At the recommended Q4_K_M quant it needs 28.6 GB of VRAM or system RAM at 8K context. Builds measured on this page range from 21.8 GB (smallest quant) to 42.7 GB (lossless). Every number below comes from the actual GGUF files - not a params x bits formula.
# llama.cpp (auto-downloads the GGUF) llama-cli -hf dealignai/MiniCPM-V-4.7-35B-A3B-CRACK-GGUF:Q4_K_M # Ollama (pulls straight from Hugging Face) ollama run hf.co/dealignai/MiniCPM-V-4.7-35B-A3B-CRACK-GGUF:Q4_K_M # LM Studio: search "dealignai/MiniCPM-V-4.7-35B-A3B-CRACK-GGUF" in the model browser
Commands load the exact quant measured on this page.
Every quantization: real file size vs what you actually need
| Quant | File (measured) | VRAM/RAM needed (8K ctx) | Runs on (first fit) |
|---|---|---|---|
| IQ2_M | 16.9 GB | 21.8 GB | RTX 3090 24GB |
| Q4_K_M | 22.6 GB | 28.6 GB | RTX 5090 32GB |
| Q8_0 | 34.3 GB | 42.7 GB | RTX PRO 6000 96GB |
KV cache uses a flat +20% context/overhead rule because this repo does not publish its config; exact numbers may differ for long contexts. MoE models keep all experts in memory — total size counts, not just active params. Longer context grows the KV cache — use the selector above.
Can I run MiniCPM-V-4.7-35B-A3B-CRACK on my GPU? (Q4_K_M recommended quant)
| Hardware | Memory | Verdict | Est. speed |
|---|---|---|---|
| RTX 3060 12GB | 12 GB | no | |
| RTX 4060 Ti 16GB | 16 GB | no | |
| RTX 3090 24GB | 24 GB | no | |
| RTX 4090 24GB | 24 GB | no | |
| RTX 5090 32GB | 32 GB | RUNS | ~60 tok/s |
| RTX PRO 6000 96GB | 96 GB | RUNS | ~60 tok/s |
| Mac 16GB unified | 16 GB | no | |
| Mac 32GB unified | 32 GB | RUNS | ~5 tok/s |
| Mac 64GB unified | 64 GB | RUNS | ~9 tok/s |
| Mac 128GB unified | 128 GB | RUNS | ~13 tok/s |
| Mac 256GB unified | 256 GB | RUNS | ~18 tok/s |
| Mac 512GB unified | 512 GB | RUNS | ~27 tok/s |
| 32GB system RAM (CPU) | 32 GB | RUNS | ~2 tok/s |
| 64GB system RAM (CPU) | 64 GB | RUNS | ~2 tok/s |
| 128GB system RAM (CPU) | 128 GB | RUNS | ~3 tok/s |
| 256GB system RAM (CPU) | 256 GB | RUNS | ~3 tok/s |
| 1TB server RAM (CPU) | 1024 GB | RUNS | ~7 tok/s |
| 2TB server RAM (CPU) | 2048 GB | RUNS | ~7 tok/s |
Speed = decode tok/s estimated from memory bandwidth ÷ measured file size (× MoE active share). Real numbers vary ±30% by runtime and settings.
How much VRAM does MiniCPM-V-4.7-35B-A3B-CRACK need?
The honest answer: 28.6 GB at the Q4_K_M quant with 8K context — that is the measured
file size (22.6 GB) plus KV cache and runtime overhead. The smallest published build needs
21.8 GB; the lossless one needs 42.7 GB.
Cheapest hardware that runs it: New RTX 5090 32GB (~$2500, used market) — see which GPU to buy.
Can I run it with CPU offload?
Yes, if combined RAM+VRAM ≥ file size — but generation speed is limited by memory bandwidth. Expect roughly: DDR5 dual channel ~10-30 tok/s for small MoE actives, single digits for big ones, 0.1-1 tok/s when experts page from disk. CPU-only is fine for batch jobs, painful for chat.
Why do other sites show different numbers?
Most pages compute weights from a formula (params × bits/8). We use the actual file sizes published in GGUF repos, which include the embedding table, unquantized tensors, and container overhead — that is why our numbers can differ from a naive calculation.
FAQ
How much VRAM does MiniCPM-V-4.7-35B-A3B-CRACK need?
The measured answer: 28.6 GB at the Q4_K_M quant with 8K context. The smallest published build needs 21.8 GB; the lossless (F16/BF16) build needs 42.7 GB. These are real GGUF file sizes from Hugging Face, not formula estimates.
Can I run MiniCPM-V-4.7-35B-A3B-CRACK on a 24GB GPU (RTX 3090/4090)?
Not at Q4_K_M (28.6 GB). Quants that fit 24GB: IQ2_M.
How fast will MiniCPM-V-4.7-35B-A3B-CRACK run?
Decode speed is memory-bandwidth-bound. At Q4_K_M: roughly 34 tok/s on an RTX 4090, 31 tok/s on an RTX 3090, 13 tok/s on an M-series Mac with 128GB, and 1.7 tok/s on CPU with dual-channel DDR4 — estimates from measured file size, MoE active-parameter share and memory bandwidth.
Can I run MiniCPM-V-4.7-35B-A3B-CRACK on CPU with system RAM?
Yes, if your usable RAM is at least the file size. At Q4_K_M you need ~28.6 GB of RAM. CPU generation is memory-bandwidth-bound: expect single-digit tok/s for large MoE models, 10-30 tok/s for small active params, and below 1 tok/s when experts page from disk.
Why do VRAM numbers for MiniCPM-V-4.7-35B-A3B-CRACK differ between sites?
Most sites compute weights from a formula (params x bits/8). ModelFit uses the actual GGUF file sizes published on Hugging Face, which include the embedding table, unquantized tensors, and container overhead — so our numbers reflect what you really download and load.