Can Hermes 4.3 36B run on RX 6800 16GB?

NO — Won't Fit

F0Won't run

Estimated from fit model

Hermes 4.3 36B needs ~28.7 GB but RX 6800 16GB only has 16.0 GB. Try a smaller quantization or lighter model.

Runtime: llama.cppCapacity: No fitBandwidth: MediumStack: StandardBottleneck: Memory capacity

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) — 28.7 GB, exceeds 16.0 GB available

28.7 GB required16.0 GB available

179% VRAM needed

12.7 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.8 tok/s

TTFT

68760 ms

Safe context

Memory

28.7 GB / 16.0 GB

Offload

40%

Memory breakdown

Weights22.0 GB

KV Cache4.2 GB

Runtime0.9 GB

Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsHermes 4.3 36B on RX 6800 16GB
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: 2.8 tok/s decode · 68.8s TTFT (warm) · 7 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 28.7 GB, but this setup only exposes 16.0 GB of usable VRAM.

Best improvement path

Add more VRAM headroom

The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	F	Too heavy	3.3 tok/s	31934 ms	4K
Coding	F	Too heavy	2.8 tok/s	68760 ms	4K
Agentic Coding	F	Too heavy	2.1 tok/s	133514 ms	4K
Reasoning	F	Too heavy	2.8 tok/s	81262 ms	4K
RAG	F	Too heavy	2.1 tok/s	166892 ms	4K

Quantization options

How Hermes 4.3 36B (36B params) fits at each quantization level on RX 6800 16GB (16.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	14.0 GB	Low	F0
Q3_K_S	3	17.6 GB	Low	F0
NVFP4	4

Upgrade options

Hardware that runs Hermes 4.3 36B well

Radeon AI PRO R9700 32GBBudget pick

32 GB VRAM (+16)640 GB/s (+128)

Makes the model fit on the accelerator instead of staying completely out of reach.17.2 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$1,899 MSRP

Radeon Pro W6800 32GBBest value

32 GB VRAM (+16)

Makes the model fit on the accelerator instead of staying completely out of reach.13.1 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$2,249 MSRP

Radeon Pro W7800 32GBAMD upgrade

32 GB VRAM (+16)576 GB/s (+64)

Makes the model fit on the accelerator instead of staying completely out of reach.15.5 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$2,499 MSRP

NVIDIA A100 40GBBiggest leap

40 GB VRAM (+24)1555 GB/s (+1043)

Makes the model fit on the accelerator instead of staying completely out of reach.59.5 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Removes host-memory offload, which is usually the single biggest latency and throughput win.

~$10,000 MSRP

Frequently asked questions

Can RX 6800 16GB run Hermes 4.3 36B?

No, Hermes 4.3 36B requires more memory than RX 6800 16GB provides.

How much VRAM does Hermes 4.3 36B need?

Hermes 4.3 36B (36B parameters) requires approximately 28.7 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 RX 6800 16GB?

On RX 6800 16GB, Hermes 4.3 36B achieves approximately 2.8 tokens per second decode speed with a time-to-first-token of 68760ms using Q4_K_M quantization.

Can RX 6800 16GB run Hermes 4.3 36B for coding?

For coding workloads, Hermes 4.3 36B on RX 6800 16GB receives a F grade with 2.8 tok/s and 4K context.

What context window can Hermes 4.3 36B use on RX 6800 16GB?

On RX 6800 16GB, Hermes 4.3 36B can safely use up to 4K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if Hermes 4.3 36B feels slow on RX 6800 16GB?

Add more VRAM headroom. The first useful upgrade is more dedicated VRAM so you can fit the model without shrinking context or dropping to a much lower quant.

See all results for RX 6800 16GB See 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-rx-6800-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: