Can the NVIDIA H100 NVL run Granite 4.2 8B?

Yes, it runs great

Runs great. At F16 it needs about 24.2 GB of 94.0 GB usable, with an estimated speed of 128 tok/s.

Best quant: F16
Generation speed: 128 tok/s
Prompt processing: 9,829 tok/s
First token (1K prompt): 0.3 s
Largest safe context: 128K

Best app to run it on the NVIDIA H100 NVL

On Linux

Inference server · runs on vLLM

The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

vllm serve ibm-granite/granite-4.2-8b

Ollama One command with Ollama’s own build of this model.
LM Studio Point-and-click: search, download and chat in one window.

On Windows

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run granite4.2:8b-bf16

LM Studio Point-and-click: search, download and chat in one window.
llama.cpp Usually the first to support new model architectures.

Want an agent? Granite 4.2 8B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Granite 4.2 8B

Recommended for the NVIDIA H100 NVL: F16. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run granite4.2:8b-bf16

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the F16 file (opens in a new tab)

huggingface.co/ibm-granite/granite-4.2-8b-GGUF (opens in a new tab)

ollama run hf.co/ibm-granite/granite-4.2-8b-GGUF:BF16

Original weights · Hugging Face

Full-precision files from IBM, for fine-tuning, vLLM, Transformers.

huggingface.co/ibm-granite/granite-4.2-8b (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from IBM. The weights themselves download from Hugging Face.

github.com/ibm-granite/granite-4.2-language-models (opens in a new tab)

git clone https://github.com/ibm-granite/granite-4.2-language-models

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at F16, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great: How well it runs on the NVIDIA H100 NVL: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	30.6 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	5.9 / 15
Match score	76.5 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA H100 NVL

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	10.2 GB	94.0 GB	894 tok/s	Runs great	47Fair quality (C) · 47 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	10.9 GB	94.0 GB	704 tok/s	Runs great	57Good quality (B) · 57 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	12.0 GB	94.0 GB	545 tok/s	Runs great	64Good quality (B) · 64 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	12.9 GB	94.0 GB	450 tok/s	Runs great	65Good quality (B) · 65 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	13.8 GB	94.0 GB	378 tok/s	Runs great	67Good quality (B) · 67 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	16.0 GB	94.0 GB	277 tok/s	Runs great	68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	24.2 GB	94.0 GB	128 tok/s	Runs great	68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q8_0 · 47.8 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q8_0 · 52.3 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti Q8_0 · 63.7 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 Q8_0 · 68.2 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 F16 · 58.7 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q8_0 · 39.2 tok/s · Runs great

Quick answers

How much memory does Granite 4.2 8B need on the NVIDIA H100 NVL 94GB?

At F16 it needs about 24.2 GB. The NVIDIA H100 NVL 94GB has 94.0 GB usable.

How fast is Granite 4.2 8B on the NVIDIA H100 NVL 94GB?

About 128 tok/s at F16, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Granite 4.2 8B should I use on the NVIDIA H100 NVL 94GB?

F16. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.