Can DeepSeek R1 0528 Qwen3 8B run on NVIDIA H100 80GB?

YES — Runs Great

C46Usable
Estimated from fit model

DeepSeek R1 0528 Qwen3 8B needs ~15.0 GB VRAM. NVIDIA H100 80GB has 80.0 GB. With Q4_K_M quantization, expect ~112 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: 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) 15.0 GB, 112.0 tok/s, Runs well
15.0 GB required80.0 GB available
19% VRAM used

Fit status

Runs well

Decode

112.0 tok/s

TTFT

1729 ms

Safe context

1.1M

Memory

15.0 GB / 80.0 GB

Memory breakdown

Weights4.9 GB
KV Cache0.9 GB
Runtime1.2 GB
Headroom8.0 GB

See how fast it feels

See how fast it feelsDeepSeek R1 0528 Qwen3 8B 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: 112.0 tok/s decode · 1.7s TTFT (warm) · 280 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
ChatCRuns well112.0 tok/s943 ms1.1M
CodingCRuns well112.0 tok/s1729 ms1.1M
Agentic CodingCRuns well112.0 tok/s2514 ms1.1M
ReasoningCRuns well112.0 tok/s2043 ms1.1M
RAGCRuns well112.0 tok/s3143 ms1.1M

Inference speed

DeepSeek R1 0528 Qwen3 8B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for DeepSeek R1 0528 Qwen3 8B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~112 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M112.0Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M112.0Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M112.0Fits
NVIDIARTX 3090 24GB
24 GBQ4_K_M112.0Fits
RX 7900 XTX 24GB
24 GBQ4_K_M112.0Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M112.0Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M95.1Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M90.2Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M77.5Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M76.8Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M76.8Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M49.2Fits
NVIDIARTX 3060 12GB
12 GBQ4_K_M48.7Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M45.1Fits
NVIDIARTX 4060 8GB
8 GBQ4_K_M40.7Offloads
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M39.6Fits

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How DeepSeek R1 0528 Qwen3 8B (8B params) fits at each quantization level on NVIDIA H100 80GB (80.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.1 GB
LowD40
Q3_K_S
3
3.9 GB
LowD40
NVFP4
4
4.5 GB
MediumD40
Q4_K_M
4
4.9 GB
MediumD40
Q5_K_M
5
5.8 GB
HighC40
Q6_K
6
6.6 GB
HighC40
Q8_0
8
8.6 GB
Very HighC40
F16Best for your GPU
16
16.4 GB
MaximumC41

Get started

Copy-paste commands to run DeepSeek R1 0528 Qwen3 8B on your machine.

Run

lms load hf-unsloth--deepseek-r1-0528-qwen3-8b-gguf && lms server start

Upgrade-Optionen

Hardware, die DeepSeek R1 0528 Qwen3 8B gut ausführt

Frequently asked questions

Can NVIDIA H100 80GB run DeepSeek R1 0528 Qwen3 8B?

Yes, NVIDIA H100 80GB can run DeepSeek R1 0528 Qwen3 8B with a C grade (Runs well). Expected decode speed: 112.0 tok/s.

How much VRAM does DeepSeek R1 0528 Qwen3 8B need?

DeepSeek R1 0528 Qwen3 8B (8B parameters) requires approximately 15.0 GB of memory with Q4_K_M quantization.

What is the best quantization for DeepSeek R1 0528 Qwen3 8B?

The recommended quantization for DeepSeek R1 0528 Qwen3 8B is Q4_K_M, which balances quality and memory efficiency.

What speed will DeepSeek R1 0528 Qwen3 8B run at on NVIDIA H100 80GB?

On NVIDIA H100 80GB, DeepSeek R1 0528 Qwen3 8B achieves approximately 112.0 tokens per second decode speed with a time-to-first-token of 1729ms using Q4_K_M quantization.

Can NVIDIA H100 80GB run DeepSeek R1 0528 Qwen3 8B for coding?

For coding workloads, DeepSeek R1 0528 Qwen3 8B on NVIDIA H100 80GB receives a C grade with 112.0 tok/s and 1.1M context.

What context window can DeepSeek R1 0528 Qwen3 8B use on NVIDIA H100 80GB?

On NVIDIA H100 80GB, DeepSeek R1 0528 Qwen3 8B can safely use up to 1.1M tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

See all results for NVIDIA H100 80GBSee all hardware for DeepSeek R1 0528 Qwen3 8B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/hf-unsloth--deepseek-r1-0528-qwen3-8b-gguf-on-h100-80gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: