Can DeepSeek R1 0528 Qwen3 8B run on H100 NVL 188GB?

YES — Runs Great

C45Usable

Estimated from fit model

DeepSeek R1 0528 Qwen3 8B needs ~25.8 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q4_K_M quantization, expect ~112 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Balanced

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) — 25.8 GB, 112.0 tok/s, Runs well

25.8 GB required188.0 GB available

14% VRAM used

Fit status

Runs well

Decode

112.0 tok/s

TTFT

1729 ms

Safe context

2.8M

Memory

25.8 GB / 188.0 GB

Memory breakdown

Weights4.9 GB

KV Cache0.9 GB

Runtime1.2 GB

Headroom18.8 GB

See how fast it feels

See how fast it feelsDeepSeek R1 0528 Qwen3 8B on H100 NVL 188GB
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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	C	Runs well	112.0 tok/s	943 ms	2.8M
Coding	C	Runs well	112.0 tok/s	1729 ms	2.8M
Agentic Coding	C	Runs well	112.0 tok/s	2514 ms	2.8M
Reasoning	C	Runs well	112.0 tok/s	2043 ms	2.8M
RAG	C	Runs well	112.0 tok/s	3143 ms	2.8M

Quantization options

How DeepSeek R1 0528 Qwen3 8B (8B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	3.1 GB	Low	D37
Q3_K_S	3	3.9 GB	Low	D37
NVFP4	4

Get started

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

Run

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

Frequently asked questions

Can H100 NVL 188GB run DeepSeek R1 0528 Qwen3 8B?

Yes, H100 NVL 188GB 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 25.8 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 H100 NVL 188GB?

On H100 NVL 188GB, 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 H100 NVL 188GB run DeepSeek R1 0528 Qwen3 8B for coding?

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

What context window can DeepSeek R1 0528 Qwen3 8B use on H100 NVL 188GB?

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

See all results for H100 NVL 188GB See 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-lmstudio-community--deepseek-r1-0528-qwen3-8b-gguf-on-h100-nvl-188gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: