Can DeepSeek V2.5 236B run on H100 NVL 188GB?
BARELY — Tight on Memory
DeepSeek V2.5 236B needs ~222.3 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q4_K_M quantization, expect ~77 tok/s.
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.
Select quantization to explore
34.3 GB over capacity — needs offload or smaller quantization
Fit status
Very compromised (needs ~22.2 GB host RAM)
Decode
76.5 tok/s
TTFT
2530 ms
Safe context
7K
Memory
222.3 GB / 188.0 GB
Offload
20%
Memory breakdown
See how fast it feels
What limits this setup
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 20% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
Best improvement path
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly 22.2 GB of extra host RAM just for the offloaded portion, before OS and other tools.
Performance by workload
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | S | Runs with offload (needs ~3.7 GB host RAM) | 96.6 tok/s | 1093 ms | 7K |
| Coding | A | Very compromised (needs ~22.2 GB host RAM) | 76.5 tok/s | 2530 ms | 7K |
| Agentic Coding | F | Too heavy | 52.0 tok/s | 5415 ms | 7K |
| Reasoning | A | Very compromised (needs ~22.2 GB host RAM) | 76.5 tok/s | 2990 ms | 7K |
| RAG | F | Too heavy | 52.0 tok/s | 6769 ms | 7K |
Quantization options
How DeepSeek V2.5 236B (236B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 92.0 GB | Low | A81 |
Q3_K_S | 3 | 115.6 GB | Low | A82 |
NVFP4 | 4 | 132.2 GB | Medium | A82 |
Q4_K_MBest for your GPU | 4 | 144.0 GB | Medium | A82 |
Q5_K_M | 5 | 169.9 GB | High | F0 |
Q6_K | 6 | 193.5 GB | High | F0 |
Q8_0 | 8 | 252.5 GB | Very High | F0 |
F16 | 16 | 483.8 GB | Maximum | F0 |
Get started
Copy-paste commands to run DeepSeek V2.5 236B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "deepseek-ai/DeepSeek-V2.5" \
--hf-file "DeepSeek-V2.5-Q4_K_M.gguf" \
-c 4096 -ngl 99Your hardware
More models your H100 NVL 188GB can run
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 284B | S | 136.1 tok/s |
Frequently asked questions
Can H100 NVL 188GB run DeepSeek V2.5 236B?
Yes, H100 NVL 188GB can run DeepSeek V2.5 236B with a A grade (Very compromised (needs ~22.2 GB host RAM)). Expected decode speed: 76.5 tok/s.
How much VRAM does DeepSeek V2.5 236B need?
DeepSeek V2.5 236B (236B parameters) requires approximately 222.3 GB of memory with Q4_K_M quantization.
What is the best quantization for DeepSeek V2.5 236B?
The recommended quantization for DeepSeek V2.5 236B is Q4_K_M, which balances quality and memory efficiency.
What speed will DeepSeek V2.5 236B run at on H100 NVL 188GB?
On H100 NVL 188GB, DeepSeek V2.5 236B achieves approximately 76.5 tokens per second decode speed with a time-to-first-token of 2530ms using Q4_K_M quantization.
Can H100 NVL 188GB run DeepSeek V2.5 236B for coding?
For coding workloads, DeepSeek V2.5 236B on H100 NVL 188GB receives a A grade with 76.5 tok/s and 7K context.
What context window can DeepSeek V2.5 236B use on H100 NVL 188GB?
On H100 NVL 188GB, DeepSeek V2.5 236B can safely use up to 7K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
What should I upgrade first if DeepSeek V2.5 236B feels slow on H100 NVL 188GB?
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/deepseek-v2.5-236b-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: