Can DeepSeek V2.5 236B run on NVIDIA H800 80GB?

Q: What should I upgrade first if DeepSeek V2.5 236B feels slow on NVIDIA H800 80GB?

Add more VRAM headroom. The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

NO — Won't Fit

F0Won't run

Estimated from fit model

DeepSeek V2.5 236B needs ~211.5 GB but NVIDIA H800 80GB only has 80.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: HighStack: StandardBottleneck: Memory capacity

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) — 211.5 GB, exceeds 80.0 GB available

211.5 GB required80.0 GB available

264% VRAM needed

131.5 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

7.8 tok/s

TTFT

24815 ms

Safe context

Memory

211.5 GB / 80.0 GB

Offload

60%

Memory breakdown

Weights144.0 GB

KV Cache58.6 GB

Runtime0.9 GB

Headroom8.0 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsDeepSeek V2.5 236B on NVIDIA H800 80GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort:

def quicksort(arr):
    if len(arr) <= 1:
        return arr
    pivot = arr[len(arr) // 2]
    left   = [x for x in arr if x < pivot]
    middle = [x for x in arr if x == pivot]
    right  = [x for x in arr if x > pivot]
    return quicksort(left) + middle + quicksort(right)

# Example usage
numbers = [3, 6, 8, 10, 1, 2, 1]
print(quicksort(numbers))  # [1, 1, 2, 3, 6, 8, 10]

The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]:
    """Sort a list using the quicksort algorithm.

    Args:
        arr: List of integers to sort.

    Returns:
        A new sorted list.
    """
    if len(arr) <= 1:
        return arr
    pivot = arr[len(arr) // 2]
    left   = [x for x in arr if x < pivot]
    middle = [x for x in arr if x == pivot]
    right  = [x for x in arr if x > pivot]
    return quicksort(left) + middle + quicksort(right)

Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 7.8 tok/s decode · 24.8s TTFT (warm) · 20 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 211.5 GB, but this setup only exposes 80.0 GB of usable VRAM.

Best improvement path

Add more VRAM headroom

The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	10.0 tok/s	10583 ms	4K
Coding	F	Too heavy	7.8 tok/s	24815 ms	4K
Agentic Coding	F	Too heavy	6.8 tok/s	41283 ms	4K
Reasoning	F	Too heavy	7.8 tok/s	29327 ms	4K
RAG	F	Too heavy	6.8 tok/s	51603 ms	4K

Quantization options

How DeepSeek V2.5 236B (236B params) fits at each quantization level on NVIDIA H800 80GB (80.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	92.0 GB	Low	F0
Q3_K_S	3	115.6 GB	Low	F0
NVFP4	4

Upgrade options

Hardware that runs DeepSeek V2.5 236B well

AMD Instinct MI350X 288GBBudget pick

288 GB VRAM (+208)8000 GB/s (+5000)

Makes the model fit on the accelerator instead of staying completely out of reach.109.3 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$8,000 MSRP

B100 192GBBest value

192 GB VRAM (+112)8000 GB/s (+5000)

Makes the model fit on the accelerator instead of staying completely out of reach.84 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 977%.

~$35,000 MSRP

NVIDIA GB200 192GBNVIDIA upgrade

192 GB VRAM (+112)8000 GB/s (+5000)

Makes the model fit on the accelerator instead of staying completely out of reach.84 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 977%.

~$60,000 MSRP

Frequently asked questions

Can NVIDIA H800 80GB run DeepSeek V2.5 236B?

No, DeepSeek V2.5 236B requires more memory than NVIDIA H800 80GB provides.

How much VRAM does DeepSeek V2.5 236B need?

DeepSeek V2.5 236B (236B parameters) requires approximately 211.5 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 NVIDIA H800 80GB?

On NVIDIA H800 80GB, DeepSeek V2.5 236B achieves approximately 7.8 tokens per second decode speed with a time-to-first-token of 24815ms using Q4_K_M quantization.

Can NVIDIA H800 80GB run DeepSeek V2.5 236B for coding?

For coding workloads, DeepSeek V2.5 236B on NVIDIA H800 80GB receives a F grade with 7.8 tok/s and 4K context.

What context window can DeepSeek V2.5 236B use on NVIDIA H800 80GB?

On NVIDIA H800 80GB, DeepSeek V2.5 236B can safely use up to 4K 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 NVIDIA H800 80GB?

See all results for NVIDIA H800 80GB See all hardware for DeepSeek V2.5 236B

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-h800-80gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: