DeepSeek Coder 6.7B Instruct on NVIDIA H100 NVL

Can the NVIDIA H100 NVL run DeepSeek Coder 6.7B Instruct?

Yes, it runs great

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

Best quant: F16
Generation speed: 167 tok/s
Prompt processing: 12,819 tok/s
First token (1K prompt): 0.3 s
Largest safe context: 16K

Best app to run it on the NVIDIA H100 NVL

On Linux

vLLM

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 deepseek-ai/deepseek-coder-6.7b-instruct

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 deepseek-coder:6.7b-instruct-fp16

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? DeepSeek Coder 6.7B Instruct 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 DeepSeek Coder 6.7B Instruct

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 deepseek-coder:6.7b-instruct-fp16

Quantized files · GGUF

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

huggingface.co/TheBloke/deepseek-coder-6.7B-instruct-GGUF (opens in a new tab)

ollama run hf.co/TheBloke/deepseek-coder-6.7B-instruct-GGUF

Original weights · Hugging Face

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

huggingface.co/deepseek-ai/deepseek-coder-6.7b-instruct (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/deepseek-ai/DeepSeek-Coder (opens in a new tab)

git clone https://github.com/deepseek-ai/DeepSeek-Coder

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

How it’s rated

Quality 34Basic quality (D) · 34 of 100: how capable the model is at F16, whatever it runs on. Match score 60/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.	15.3 / 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.7 / 15
Match score	61.0 / 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`	12.3 GB	94.0 GB	1,167 tok/s	Runs great	23Basic quality (D) · 23 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	12.9 GB	94.0 GB	918 tok/s	Runs great	28Basic quality (D) · 28 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	13.7 GB	94.0 GB	710 tok/s	Runs great	32Basic quality (D) · 32 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	14.4 GB	94.0 GB	587 tok/s	Runs great	32Basic quality (D) · 32 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	15.1 GB	94.0 GB	493 tok/s	Runs great	33Basic quality (D) · 33 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	16.7 GB	94.0 GB	362 tok/s	Runs great	34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	23.1 GB	94.0 GB	167 tok/s	Runs great	34Basic quality (D) · 34 of 100: how capable the model is at F16, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.	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

34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q8_0 · 51.1 tok/s · Runs great
34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q8_0 · 62.3 tok/s · Runs great
34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q8_0 · 68.2 tok/s · Runs great
34Basic quality (D) · 34 of 100: how capable the model is at F16, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 F16 · 43.1 tok/s · Runs great
34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5060 Ti 16GB Q8_0 · 41.5 tok/s · Runs great
34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti Q8_0 · 83.1 tok/s · Runs great

Quick answers

How much memory does DeepSeek Coder 6.7B Instruct need on the NVIDIA H100 NVL 94GB?

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

How fast is DeepSeek Coder 6.7B Instruct on the NVIDIA H100 NVL 94GB?

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

Which quantization of DeepSeek Coder 6.7B Instruct 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.