DeepSeek Coder V2 Instruct (0614) on NVIDIA H100 NVL

Can the NVIDIA H100 NVL run DeepSeek Coder V2 Instruct (0614)?

Yes, it runs well (offloads to RAM)

Runs well (offloads to RAM). At Q2_K it needs about 100 GB of 94.0 GB usable, with an estimated speed of 63.2 tok/s.

Best quant: Q2_K
Generation speed: 63.2 tok/s
Prompt processing: 3,926 tok/s
First token (1K prompt): 0.3 s
Largest safe context: —

Best app to run it on the NVIDIA H100 NVL

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open DeepSeek Coder V2 Instruct (0614) in LM Studio

Ollama Splits the model between GPU memory and system RAM, which this setup needs.
llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

Splits the model between GPU memory and system RAM, which this setup needs.
Point-and-click: search, download and chat in one window.

Open DeepSeek Coder V2 Instruct (0614) in LM Studio

Ollama Splits the model between GPU memory and system RAM, which this setup needs.
llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.

Want an agent? DeepSeek Coder V2 Instruct (0614) 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 V2 Instruct (0614)

Recommended for the NVIDIA H100 NVL: Q2_K. 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-v2:236b-instruct-q2_K

Quantized files · GGUF

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

Download the Q2_K files (opens in a new tab)

huggingface.co/bartowski/DeepSeek-Coder-V2-Instruct-GGUF (opens in a new tab)

ollama run hf.co/bartowski/DeepSeek-Coder-V2-Instruct-GGUF

Original weights · Hugging Face

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

huggingface.co/deepseek-ai/DeepSeek-Coder-V2-Instruct (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q2_K, 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 welloffloads to RAM: 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.	22.7 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	10.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.	15.0 / 15
Match score	62.7 / 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`	100 GB	94.0 GB	63.2 tok/s	Runs welloffloads to RAM	50Fair quality (C) · 50 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q3_K_M`	121 GB	94.0 GB	—	Won't run	60Good quality (B) · 60 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q4_K_M`	150 GB	94.0 GB	—	Won't run	68Good quality (B) · 68 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q5_K_M`	173 GB	94.0 GB	—	Won't run	69Good quality (B) · 69 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.
`Q6_K`	199 GB	94.0 GB	—	Won't run	71Great quality (A) · 71 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.
`Q8_0`	256 GB	94.0 GB	—	Won't run	72Great quality (A) · 72 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.
`F16`	477 GB	94.0 GB	—	Won't run	72Great quality (A) · 72 of 100: how capable the model is at F16, whatever it runs on. Match score 9/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

68Good quality (B) · 68 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (256 GB) Q4_K_M · 36.2 tok/s · Runs great
60Good quality (B) · 60 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) Q3_K_M · 44.5 tok/s · Runs well (tight fit)
68Good quality (B) · 68 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (512 GB) Q4_K_M · 36.2 tok/s · Runs great
50Fair quality (C) · 50 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB10 (128 GB) Q2_K · 24.2 tok/s · Runs well (tight fit)
50Fair quality (C) · 50 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q2_K · 63.5 tok/s · Runs well (offloads to RAM)
50Fair quality (C) · 50 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) Q2_K · 33.6 tok/s · Runs well (over GPU memory limit)

Quick answers

How much memory does DeepSeek Coder V2 Instruct (0614) need on the NVIDIA H100 NVL 94GB?

At Q2_K it needs about 100 GB. The NVIDIA H100 NVL 94GB has 94.0 GB usable.

How fast is DeepSeek Coder V2 Instruct (0614) on the NVIDIA H100 NVL 94GB?

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

Which quantization of DeepSeek Coder V2 Instruct (0614) should I use on the NVIDIA H100 NVL 94GB?

Q2_K. 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.