Nemotron 3.5 Bolt 74B-A9B on NVIDIA H200 141GB SXM
Can the NVIDIA H200 141GB SXM run Nemotron 3.5 Bolt 74B-A9B?
Yes, it runs great
Runs great. At Q8_0 it needs about 87.1 GB of 141 GB usable, with an estimated speed of 147 tok/s.
- Best quant
Q8_0- Generation speed
- 147 tok/s
- Prompt processing
- 10,704 tok/s
- First token (1K prompt)
- 0.3 s
- Largest safe context
- 256K
Best app to run it on the NVIDIA H200 141GB SXM
On Linux
- 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 nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-BF16On Windows
- 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 nemotron-3.5-bolt:74b-a9bDownload Nemotron 3.5 Bolt 74B-A9B
Recommended for the NVIDIA H200 141GB SXM: Q8_0. 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.
ollama run nemotron-3.5-bolt:74b-a9bQuantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
Download the Q8_0 files (opens in a new tab)
huggingface.co/unsloth/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-GGUF (opens in a new tab)
ollama run hf.co/unsloth/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-GGUFOriginal weights · Hugging Face
Full-precision files from NVIDIA, for fine-tuning, vLLM, Transformers.
huggingface.co/nvidia/NVIDIA-Nemotron-3.5-Bolt-74B-A9B-BF16 (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from NVIDIA. The weights themselves download from Hugging Face.
github.com/NVIDIA-NeMo/Nemotron (opens in a new tab)
git clone https://github.com/NVIDIA-NeMo/NemotronHow it’s rated
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 quality | 41.6 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Memory use | 14.3 / 15 | |
| Match score | 95.9 / 100 |
Every quantization on the NVIDIA H200 141GB SXM
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q2_K | 37.7 GB | 141 GB | 247 tok/s | Runs great | 64Good quality (B) · 64 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (UD-Q2_K_XL) (opens in a new tab) |
Q3_K_M | 44.4 GB | 141 GB | 226 tok/s | Runs great | 77Great quality (A) · 77 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (UD-Q3_K_XL) (opens in a new tab) |
Q4_K_M | 53.4 GB | 141 GB | 204 tok/s | Runs great | 87Excellent quality (A+) · 87 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (UD-Q4_K_XL) · folder (opens in a new tab) |
Q5_K_M | 60.9 GB | 141 GB | 187 tok/s | Runs great | 89Excellent quality (A+) · 89 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (UD-Q5_K_XL) · folder (opens in a new tab) |
Q6_K | 69.1 GB | 141 GB | 172 tok/s | Runs great | 91Excellent quality (A+) · 91 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (UD-Q6_K_XL) · folder (opens in a new tab) |
Q8_0 | 87.1 GB | 141 GB | 147 tok/s | Runs great | 92Excellent quality (A+) · 92 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking. | GGUF · folder (opens in a new tab) |
F16 | 157 GB | 141 GB | 16.2 tok/s | Runs welloffloads to RAM | 92Excellent quality (A+) · 92 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 · folder (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
-
92Excellent quality (A+) · 92 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 96/100 (quality, fit, speed and memory use) sets the ranking.
Apple M2 Ultra (192 GB)
-
91Excellent quality (A+) · 91 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 96/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
91Excellent quality (A+) · 91 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 95/100 (quality, fit, speed and memory use) sets the ranking.
Apple M4 Max (128 GB)
-
92Excellent quality (A+) · 92 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 93/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (256 GB)
-
87Excellent quality (A+) · 87 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)
-
87Excellent quality (A+) · 87 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking.
AMD Ryzen AI Max+ 395 (128 GB)
Quick answers
How much memory does Nemotron 3.5 Bolt 74B-A9B need on the NVIDIA H200 141GB SXM?
At Q8_0 it needs about 87.1 GB. The NVIDIA H200 141GB SXM has 141 GB usable.
How fast is Nemotron 3.5 Bolt 74B-A9B on the NVIDIA H200 141GB SXM?
About 147 tok/s at Q8_0, an estimate from the hardware’s memory bandwidth and the size of the model.
Which quantization of Nemotron 3.5 Bolt 74B-A9B should I use on the NVIDIA H200 141GB SXM?
Q8_0. 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.