Can Devstral 2 123B Instruct run on NVIDIA H100 80GB?

BARELY — Tight on Memory

A83Great

Estimated from fit model

Devstral 2 123B Instruct needs ~89.3 GB VRAM. NVIDIA H100 80GB has 80.0 GB. With Q4_K_M quantization, expect ~29 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: HighStack: StandardBottleneck: Host offload

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) — 89.3 GB, 29.0 tok/s, Very compromised (needs ~7.8 GB host RAM)

89.3 GB required80.0 GB available

112% VRAM needed

9.3 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~7.8 GB host RAM)

Decode

29.0 tok/s

TTFT

6672 ms

Safe context

Memory

89.3 GB / 80.0 GB

Offload

10%

Memory breakdown

Weights75.0 GB

KV Cache5.4 GB

Runtime0.9 GB

Headroom8.0 GB

See how fast it feels

See how fast it feelsDevstral 2 123B Instruct on NVIDIA H100 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: 29.0 tok/s decode · 6.7s TTFT (warm) · 73 tok/s prefill

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 10% 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 7.8 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	A	Very compromised (needs ~5.7 GB host RAM)	30.5 tok/s	3461 ms	4K
Coding	A	Very compromised (needs ~7.8 GB host RAM)	29.0 tok/s	6672 ms	4K
Agentic Coding	A	Very compromised (needs ~11.6 GB host RAM)	26.3 tok/s	10687 ms	4K
Reasoning	A	Very compromised (needs ~7.8 GB host RAM)	29.0 tok/s	7886 ms	4K
RAG	A	Very compromised (needs ~11.6 GB host RAM)	26.3 tok/s	13359 ms	4K

Inference speed

Devstral 2 123B Instruct inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Devstral 2 123B Instruct at Q4_K_M across popular GPUs and Apple Silicon, including multi-GPU rigs, using the fastest local runtime per device. Fastest is MacBook Pro M4 Max 128GB at ~8 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 / Mac	Memory	Quant	Speed (tok/s)	Fits?
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	8.2	Offloads
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	8.1	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	6.3	Offloads
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	6.0	Offloads
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	3.9	Too big
2× RX 7900 XTX 24GB	48 GB	Q4_K_M	3.7	Too big
2× RTX 4090 24GB	48 GB	Q4_K_M	2.6	Too big
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	2.5	Too big
2× RTX 3090 24GB	48 GB	Q4_K_M	2.2	Too big
RTX 5090 32GB	32 GB	Q4_K_M	2.0	Too big
RTX 4090 24GB	24 GB	Q4_K_M	2.0	Too big
RTX 4080 Super 16GB	16 GB	Q4_K_M	2.0	Too big
RTX 3090 24GB	24 GB	Q4_K_M	2.0	Too big
RTX 4070 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 3060 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 4060 8GB	8 GB	Q4_K_M	2.0	Too big
RX 7900 XTX 24GB	24 GB	Q4_K_M	2.0	Too big
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	2.0	Too big
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	2.0	Too big
4× RTX 3060 12GB	48 GB	Q4_K_M	2.0	Too big

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 Devstral 2 123B Instruct (123B params) fits at each quantization level on NVIDIA H100 80GB (80.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	48.0 GB	Low	S91
Q3_K_SBest for your GPU	3	60.3 GB	Low	S91
NVFP4	4	68.9 GB	Medium	F0
Q4_K_M	4	75.0 GB	Medium	F0
Q5_K_M	5	88.6 GB	High	F0
Q6_K	6	100.9 GB	High	F0
Q8_0	8	131.6 GB	Very High	F0
F16	16	252.2 GB	Maximum	F0

Get started

Copy-paste commands to run Devstral 2 123B Instruct on your machine.

Run

lms load Devstral-2-123B-Instruct-2512 && lms server start

Frequently asked questions

Can NVIDIA H100 80GB run Devstral 2 123B Instruct?

Yes, NVIDIA H100 80GB can run Devstral 2 123B Instruct with a A grade (Very compromised (needs ~7.8 GB host RAM)). Expected decode speed: 29.0 tok/s.

How much VRAM does Devstral 2 123B Instruct need?

Devstral 2 123B Instruct (123B parameters) requires approximately 89.3 GB of memory with Q4_K_M quantization.

What is the best quantization for Devstral 2 123B Instruct?

The recommended quantization for Devstral 2 123B Instruct is Q4_K_M, which balances quality and memory efficiency.

What speed will Devstral 2 123B Instruct run at on NVIDIA H100 80GB?

On NVIDIA H100 80GB, Devstral 2 123B Instruct achieves approximately 29.0 tokens per second decode speed with a time-to-first-token of 6672ms using Q4_K_M quantization.

Can NVIDIA H100 80GB run Devstral 2 123B Instruct for coding?

For coding workloads, Devstral 2 123B Instruct on NVIDIA H100 80GB receives a A grade with 29.0 tok/s and 4K context.

What context window can Devstral 2 123B Instruct use on NVIDIA H100 80GB?

On NVIDIA H100 80GB, Devstral 2 123B Instruct can safely use up to 4K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.

What should I upgrade first if Devstral 2 123B Instruct feels slow on NVIDIA H100 80GB?

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.

See all results for NVIDIA H100 80GB See all hardware for Devstral 2 123B Instruct

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/devstral-2-123b-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: