Can the RTX 6000D run Granite 4.2 3B?

Yes. Granite 4.2 3B fits the RTX 6000D's 84 GB at Q4_K_M (about 3.8 GB needed), running at an estimated 450 tok/s. There's room for up to FP16 if you want higher quality.

VRAM
84 GB
Needs at Q4
3.8 GB
Headroom
80.2 GB
Speed (Q4_K_M)
~450 tok/s

Every quantization

Granite 4.2 3B (3.7B) on 84 GB

QuantWeightsNeedsFitEst. speed
Q4_K_M2 GB3.8 GBFits easily~450 tok/s
Q5_K_M3 GB4.8 GBFits easily~300 tok/s
Q8_04 GB5.8 GBFits easily~225 tok/s
FP167 GB8.8 GBFits easily~129 tok/s

Estimates. Needs = weights + 1.8 GB for KV cache and runtime at modest context. Speed is single-stream decode scaled from the RTX 6000D's 1570 GB/s bandwidth (Estimated from memory bandwidth (llama.cpp decode)). Long contexts need more memory and run slower.

Run it

Copy, paste, go

llama-server -hf ibm-granite/granite-4.2-3b-GGUF -ngl 99

Ollama pulls a Q4 build by default. Pick a larger quant only if the table above says it fits. Full Granite 4.2 3B details →

Compare

Same model, other hardware - and other models on this card

Granite 4.2 3B on other hardware

Also runs on the RTX 6000D

Frequently asked

Quick answers

Can the RTX 6000D run Granite 4.2 3B?

Yes. Granite 4.2 3B fits the RTX 6000D's 84 GB at Q4_K_M (about 3.8 GB needed), running at an estimated 450 tok/s. There's room for up to FP16 if you want higher quality.

How much VRAM does Granite 4.2 3B need?

About 2 GB of weights at Q4_K_M, 4 GB at Q8_0 and 7 GB at FP16. Add roughly 1.8 GB for the KV cache and runtime at modest context lengths.

How fast is Granite 4.2 3B on the RTX 6000D?

Roughly 450 tokens per second at Q4_K_M (single user, llama.cpp-style decode). This is an estimate from the RTX 6000D's 1570 GB/s memory bandwidth.