Can Codestral 2 25.08 run on H100 NVL 188GB?

YES — Runs Great

A80Great

Estimated from fit model

Codestral 2 25.08 needs ~35.6 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q4_K_M quantization, expect ~308 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: 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) — 35.6 GB, 308.0 tok/s, Runs well

35.6 GB required188.0 GB available

19% VRAM used

Fit status

Runs well

Decode

308.0 tok/s

TTFT

629 ms

Safe context

256K

Memory

35.6 GB / 188.0 GB

Memory breakdown

Weights13.4 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom18.8 GB

See how fast it feels

See how fast it feelsCodestral 2 25.08 on H100 NVL 188GB
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: 308.0 tok/s decode · 629ms TTFT (warm) · 770 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	A	Runs well	308.0 tok/s	350 ms	256K
Coding	A	Runs well	308.0 tok/s	629 ms	256K
Agentic Coding	A	Runs well	308.0 tok/s	914 ms	256K
Reasoning	A	Runs well	308.0 tok/s	743 ms	256K
RAG	A	Runs well	308.0 tok/s	1143 ms	256K

Quantization options

How Codestral 2 25.08 (22B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	8.6 GB	Low	A71
Q3_K_S	3	10.8 GB	Low	A71
NVFP4	4	12.3 GB	Medium	A71
Q4_K_M	4	13.4 GB	Medium	A71
Q5_K_M	5	15.8 GB	High	A72
Q6_K	6	18.0 GB	High	A72
Q8_0	8	23.5 GB	Very High	A72
F16Best for your GPU	16	45.1 GB	Maximum	A75

Get started

Copy-paste commands to run Codestral 2 25.08 on your machine.

Run

lms load codestral-2508 && lms server start

Your hardware

More models your H100 NVL 188GB can run

Model	Params	Grade	Decode
Devstral 2 123B Instruct	123B	S	91.6 tok/s
Qwen3-Coder 30B A3B Instruct	30.5B	S	955.4 tok/s
Qwen 3.5 27B	27B	S	378 tok/s
Qwen 3.6 27B	27B	S	258.3 tok/s
Qwen 3.5 122B A10B	122B	S	254 tok/s

Frequently asked questions

Can H100 NVL 188GB run Codestral 2 25.08?

Yes, H100 NVL 188GB can run Codestral 2 25.08 with a A grade (Runs well). Expected decode speed: 308.0 tok/s.

How much VRAM does Codestral 2 25.08 need?

Codestral 2 25.08 (22B parameters) requires approximately 35.6 GB of memory with Q4_K_M quantization.

What is the best quantization for Codestral 2 25.08?

The recommended quantization for Codestral 2 25.08 is Q4_K_M, which balances quality and memory efficiency.

What speed will Codestral 2 25.08 run at on H100 NVL 188GB?

On H100 NVL 188GB, Codestral 2 25.08 achieves approximately 308.0 tokens per second decode speed with a time-to-first-token of 629ms using Q4_K_M quantization.

Can H100 NVL 188GB run Codestral 2 25.08 for coding?

For coding workloads, Codestral 2 25.08 on H100 NVL 188GB receives a A grade with 308.0 tok/s and 256K context.

What context window can Codestral 2 25.08 use on H100 NVL 188GB?

On H100 NVL 188GB, Codestral 2 25.08 can safely use up to 256K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.

See all results for H100 NVL 188GB See all hardware for Codestral 2 25.08

Embed this result▼

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

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