Can Granite 4.1 30B run on H100 NVL 188GB?

YES — Runs Great

A79Great

Estimated from fit model

Granite 4.1 30B needs ~42.2 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q4_K_M quantization, expect ~371 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) — 42.2 GB, 371.1 tok/s, Runs well

42.2 GB required188.0 GB available

22% VRAM used

Fit status

Runs well

Decode

371.1 tok/s

TTFT

522 ms

Safe context

131K

Memory

42.2 GB / 188.0 GB

Memory breakdown

Weights18.3 GB

KV Cache3.9 GB

Runtime1.2 GB

Headroom18.8 GB

See how fast it feels

See how fast it feelsGranite 4.1 30B 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: 371.1 tok/s decode · 522ms TTFT (warm) · 928 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	371.1 tok/s	350 ms	131K
Coding	A	Runs well	371.1 tok/s	522 ms	131K
Agentic Coding	A	Runs well	345.2 tok/s	816 ms	131K
Reasoning	A	Runs well	371.1 tok/s	616 ms	131K
RAG	A	Runs well	371.1 tok/s	948 ms	131K

Quantization options

How Granite 4.1 30B (30B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	11.7 GB	Low	B69
Q3_K_S	3	14.7 GB	Low	B70
NVFP4	4	16.8 GB	Medium	B70
Q4_K_M	4	18.3 GB	Medium	B70
Q5_K_M	5	21.6 GB	High	A70
Q6_K	6	24.6 GB	High	A70
Q8_0	8	32.1 GB	Very High	A71
F16Best for your GPU	16	61.5 GB	Maximum	A75

Get started

Copy-paste commands to run Granite 4.1 30B on your machine.

Run

ollama run granite4.1:30b

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 122B A10B	122B	S	254 tok/s
DeepSeek V4 Flash	284B	S	136.1 tok/s
Qwen 3.6 35B A3B	35B	S	802.9 tok/s

Frequently asked questions

Can H100 NVL 188GB run Granite 4.1 30B?

Yes, H100 NVL 188GB can run Granite 4.1 30B with a A grade (Runs well). Expected decode speed: 371.1 tok/s.

How much VRAM does Granite 4.1 30B need?

Granite 4.1 30B (30B parameters) requires approximately 42.2 GB of memory with Q4_K_M quantization.

What is the best quantization for Granite 4.1 30B?

The recommended quantization for Granite 4.1 30B is Q4_K_M, which balances quality and memory efficiency.

What speed will Granite 4.1 30B run at on H100 NVL 188GB?

On H100 NVL 188GB, Granite 4.1 30B achieves approximately 371.1 tokens per second decode speed with a time-to-first-token of 522ms using Q4_K_M quantization.

Can H100 NVL 188GB run Granite 4.1 30B for coding?

For coding workloads, Granite 4.1 30B on H100 NVL 188GB receives a A grade with 371.1 tok/s and 131K context.

What context window can Granite 4.1 30B use on H100 NVL 188GB?

On H100 NVL 188GB, Granite 4.1 30B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

See all results for H100 NVL 188GB See all hardware for Granite 4.1 30B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/granite-4.1-30b-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: