willitrun·ai

Can Hermes 4.3 36B run on NVIDIA H200 PCIe 141GB?

YES — Runs Great

C48Usable
Estimated from fit model

Hermes 4.3 36B needs ~41.5 GB VRAM. NVIDIA H200 PCIe 141GB has 141.0 GB. With Q4_K_M quantization, expect ~184 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: HighStack: BasicBottleneck: Balanced
Share:

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) 41.5 GB, 183.6 tok/s, Runs well
41.5 GB required141.0 GB available
29% VRAM used

Fit status

Runs well

Decode

183.6 tok/s

TTFT

1054 ms

Safe context

393K

Memory

41.5 GB / 141.0 GB

Memory breakdown

Weights22.0 GB
KV Cache4.2 GB
Runtime1.2 GB
Headroom14.1 GB

See how fast it feels

See how fast it feelsHermes 4.3 36B on NVIDIA H200 PCIe 141GB
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: 183.6 tok/s decode · 1.1s TTFT (warm) · 459 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

WorkloadGradeFitDecodeTTFTContext
ChatCRuns well183.6 tok/s575 ms393K
CodingCRuns well183.6 tok/s1054 ms393K
Agentic CodingCRuns well183.6 tok/s1534 ms393K
ReasoningCRuns well183.6 tok/s1246 ms393K
RAGCRuns well183.6 tok/s1917 ms393K

Inference speed

Hermes 4.3 36B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Hermes 4.3 36B at Q4_K_M across popular GPUs and Apple Silicon, including multi-GPU rigs, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~55 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 / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M54.7Offloads
2× RX 7900 XTX 24GB
48 GBQ4_K_M53.5Fits
NVIDIA2× RTX 4090 24GB
48 GBQ4_K_M28.1Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M27.3Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M27.3Fits
NVIDIA2× RTX 3090 24GB
48 GBQ4_K_M25.8Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M25.4Fits
NVIDIA4× RTX 3060 12GB
48 GBQ4_K_M22.7Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M21.1Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M20.0Fits
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M17.2Tight
NVIDIARTX 4090 24GB
24 GBQ4_K_M16.6Too big
RX 7900 XTX 24GB
24 GBQ4_K_M15.3Too big
NVIDIARTX 3090 24GB
24 GBQ4_K_M14.2Too big
MacBook Pro M3 Max 64GB
64 GBQ4_K_M10.9Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M10.0Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M6.0Too big
NVIDIARTX 4070 12GB
12 GBQ4_K_M2.6Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M2.0Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.0Too 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 Hermes 4.3 36B (36B params) fits at each quantization level on NVIDIA H200 PCIe 141GB (141.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
14.0 GB
LowD38
Q3_K_S
3
17.6 GB
LowD38
NVFP4
4
20.2 GB
MediumD39
Q4_K_M
4
22.0 GB
MediumD39
Q5_K_M
5
25.9 GB
HighD39
Q6_K
6
29.5 GB
HighD40
Q8_0
8
38.5 GB
Very HighC41
F16Best for your GPU
16
73.8 GB
MaximumC46

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

Can NVIDIA H200 PCIe 141GB run Hermes 4.3 36B?

Yes, NVIDIA H200 PCIe 141GB can run Hermes 4.3 36B with a C grade (Runs well). Expected decode speed: 183.6 tok/s.

How much VRAM does Hermes 4.3 36B need?

Hermes 4.3 36B (36B parameters) requires approximately 41.5 GB of memory with Q4_K_M quantization.

What is the best quantization for Hermes 4.3 36B?

The recommended quantization for Hermes 4.3 36B is Q4_K_M, which balances quality and memory efficiency.

What speed will Hermes 4.3 36B run at on NVIDIA H200 PCIe 141GB?

On NVIDIA H200 PCIe 141GB, Hermes 4.3 36B achieves approximately 183.6 tokens per second decode speed with a time-to-first-token of 1054ms using Q4_K_M quantization.

Can NVIDIA H200 PCIe 141GB run Hermes 4.3 36B for coding?

For coding workloads, Hermes 4.3 36B on NVIDIA H200 PCIe 141GB receives a C grade with 183.6 tok/s and 393K context.

What context window can Hermes 4.3 36B use on NVIDIA H200 PCIe 141GB?

On NVIDIA H200 PCIe 141GB, Hermes 4.3 36B can safely use up to 393K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

See all results for NVIDIA H200 PCIe 141GBSee all hardware for Hermes 4.3 36B
Embed this result

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

<iframe src="https://willitrunai.com/embed/hf-nousresearch--hermes-4-3-36b-gguf-on-h200-pcie-141gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: