Can Hermes 4.3 36B run on H100 NVL 188GB?

YES — Runs Great

C47Usable

○Estimated from fit model

Hermes 4.3 36B needs ~46.2 GB VRAM. H100 NVL 188GB has 188.0 GB. With Q4_K_M quantization, expect ~288 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) — 46.2 GB, 287.7 tok/s, Runs well

46.2 GB required188.0 GB available

25% VRAM used

Fit status

Runs well

Decode

287.7 tok/s

TTFT

673 ms

Safe context

554K

Memory

46.2 GB / 188.0 GB

Memory breakdown

Weights22.0 GB

KV Cache4.2 GB

Runtime1.2 GB

Headroom18.8 GB

See how fast it feels

See how fast it feelsHermes 4.3 36B on H100 NVL 188GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step.

Given information:
 - Speed = 60 mph (miles per hour)
 - Time = 2.5 hours

Formula: Distance = Speed x Time

Calculation:
 Distance = 60 mph x 2.5 h
 = 150 miles

The train travels 150 miles.

Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time.

Breakdown:
 - First half: 1.25 hours at 60 mph = 75 miles
 - Stop: 20 minutes (no distance)
 - Second half: 1.25 hours at 60 mph = 75 miles

Total distance: 150 miles (same)
Total time: 2.5 h + 0.33 h = 2.83 hours
Average speed: 150 / 2.83 = 53 mph

The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 287.7 tok/s decode · 673ms TTFT (warm) · 719 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	C	Runs well	287.7 tok/s	367 ms	554K
Coding	C	Runs well	287.7 tok/s	673 ms	554K
Agentic Coding	C	Runs well	287.7 tok/s	979 ms	554K
Reasoning	C	Runs well	287.7 tok/s	795 ms	554K
RAG	C	Runs well	287.7 tok/s	1223 ms	554K

Quantization options

How Hermes 4.3 36B (36B params) fits at each quantization level on H100 NVL 188GB (188.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	14.0 GB	Low	D37
Q3_K_S	3	17.6 GB	Low	D37
NVFP4	4	20.2 GB	Medium	D37
Q4_K_M	4	22.0 GB	Medium	D38
Q5_K_M	5	25.9 GB	High	D38
Q6_K	6	29.5 GB	High	D39
Q8_0	8	38.5 GB	Very High	D40
F16Best for your GPU	16	73.8 GB	Maximum	C44

Get started

Copy-paste commands to run Hermes 4.3 36B on your machine.

Run

lms load hf-nousresearch--hermes-4-3-36b-gguf && lms server start

Frequently asked questions

See all results for H100 NVL 188GB See all hardware for Hermes 4.3 36B

URL: https://willitrunai.com/can-run/hf-nousresearch--hermes-4-3-36b-gguf-on-h100-nvl-188gb