Yes — with 185.9 GB to spare
Granite 4.1 30B at Q4_K_M fits your CPU only · DDR5 8-channel server entirely on the GPU at 8K context, at an estimated 7.9 tokens per second. There is room for its full 128K window.
Fully on GPU
8K context
Q4_K_M · 16.3 GB
Apache 2.0
Released 29 Apr 2026
The largest Granite. Dense 29B at Q4 is a comfortable 24 GB fit.
The VRAM budget
weights 16.3 GB
Weights 16.3 GB
KV cache @ 8K 2.00 GB
Runtime overhead 0.6 GB
Free 185.9 GB of 204.8 GB
Quantisation ladder
| Quant | Weights | Total @ 8K | Max context | Tok/s | Quality | Fit |
|---|---|---|---|---|---|---|
| Q8_0 | 28.6 GB | 31.2 GB | 128K | 4.5 | −0.1% ppl | Long context |
| Q6_K | 22.1 GB | 24.7 GB | 128K | 5.8 | −0.4% ppl | Long context |
| Q5_K_M | 19.1 GB | 21.7 GB | 128K | 6.7 | −0.8% ppl | Long context |
| Q4_K_M | 16.3 GB | 18.9 GB | 128K | 7.9 | −1.9% ppl | Recommended |
| Q3_K_M | 13.2 GB | 15.8 GB | 128K | 9.8 | −5.4% ppl | Long context |
| Q2_K | 11.3 GB | 13.9 GB | 128K | 11 | −15% ppl | Long context |
Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it.
How to run it
$ llama-server \
-hf ibm-granite/granite-4.1-30b:Q4_K_M \
-c 8192 -ngl 99
The engine underneath most of the others. Every knob is exposed. More on llama.cpp.
01Download is 16.3 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02With no GPU, thread count matters more than clock. Start at one thread per physical core.
03There is room to go to the model's full 128K context on this card.