VOOZH about

URL: https://willitrunai.com/can-run/deepseek-llm-67b-on-h100-80gb


Can DeepSeek LLM 67B run on NVIDIA H100 80GB?

YES — Runs Great

B66Good
Estimated from fit model

DeepSeek LLM 67B needs ~55.6 GB VRAM. NVIDIA H100 80GB has 80.0 GB. With Q4_K_M quantization, expect ~69 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: Balanced
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 55.6 GB, 74.9 tok/s, Runs well
55.6 GB required80.0 GB available
70% VRAM used

Fit status

Runs well

Decode

74.9 tok/s

TTFT

2586 ms

Safe context

4K

Memory

55.6 GB / 80.0 GB

Memory breakdown

Weights40.9 GB
KV Cache5.8 GB
Runtime0.9 GB
Headroom8.0 GB

See how fast it feels

See how fast it feelsDeepSeek LLM 67B on NVIDIA H100 80GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 74.9 tok/s decode · 2.6s TTFT (warm) · 187 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatBRuns well68.9 tok/s1534 ms4K
CodingBRuns well68.9 tok/s2812 ms4K
Agentic CodingBRuns well68.9 tok/s4090 ms4K
ReasoningBRuns well68.9 tok/s3323 ms4K
RAGBRuns well68.9 tok/s5112 ms4K

Quantization options

How DeepSeek LLM 67B (67B params) fits at each quantization level on NVIDIA H100 80GB (80.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
26.1 GB
LowC53
Q3_K_S
3
32.8 GB
LowC55
NVFP4
4

Get started

Copy-paste commands to run DeepSeek LLM 67B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "deepseek-ai/deepseek-llm-67b-chat" \ --hf-file "deepseek-llm-67b-chat-Q4_K_M.gguf" \ -c 4096 -ngl 99

Frequently asked questions

See all results for NVIDIA H100 80GBSee all hardware for DeepSeek LLM 67B
37.5 GB
Medium
B56
Q4_K_M
4
40.9 GB
MediumB57
Q5_K_M
5
48.2 GB
HighB58
Q6_KBest for your GPU
6
54.9 GB
HighB58
Q8_0
8
71.7 GB
Very HighF0
F16
16
137.4 GB
MaximumF0