Can Yi 1.5 34B run on RX 6800 XT 16GB?

NO — Won't Fit

F0Won't run

Estimated from fit model

Yi 1.5 34B needs ~26.9 GB but RX 6800 XT 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) — 26.9 GB, exceeds 16.0 GB available

26.9 GB required16.0 GB available

168% VRAM needed

10.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

3.8 tok/s

TTFT

51346 ms

Safe context

Memory

26.9 GB / 16.0 GB

Offload

40%

Memory breakdown

Weights20.7 GB

KV Cache3.7 GB

Runtime0.9 GB

Headroom1.6 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsYi 1.5 34B on RX 6800 XT 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: 3.8 tok/s decode · 51.3s TTFT (warm) · 9 tok/s prefill

What limits this setup

Usable VRAM is the main blocker for this model.

Not enough usable memory

The model needs 26.9 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	4.4 tok/s	24145 ms	4K
Coding	F	Too heavy	3.8 tok/s	51346 ms	4K
Agentic Coding	F	Too heavy	2.7 tok/s	106078 ms	4K
Reasoning	F	Too heavy	3.8 tok/s	60682 ms	4K
RAG	F	Too heavy	2.9 tok/s	122129 ms	4K

Quantization options

How Yi 1.5 34B (34B params) fits at each quantization level on RX 6800 XT 16GB (16.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	13.3 GB	Low	F0
Q3_K_S	3	16.7 GB	Low	F0
NVFP4	4

Upgrade options

Hardware that runs Yi 1.5 34B well

RX 7900 XTX 24GBBest value

24 GB VRAM (+8)960 GB/s (+448)

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

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

Raises estimated decode speed by about 429%.

~$999 MSRP

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.19.8 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 32GBAMD upgrade

32 GB VRAM (+16)

Makes the model fit on the accelerator instead of staying completely out of reach.15 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

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.68.4 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 XT 16GB run Yi 1.5 34B?

No, Yi 1.5 34B requires more memory than RX 6800 XT 16GB provides.

How much VRAM does Yi 1.5 34B need?

Yi 1.5 34B (34B parameters) requires approximately 26.9 GB of memory with Q4_K_M quantization.

What is the best quantization for Yi 1.5 34B?

The recommended quantization for Yi 1.5 34B is Q4_K_M, which balances quality and memory efficiency.

What speed will Yi 1.5 34B run at on RX 6800 XT 16GB?

On RX 6800 XT 16GB, Yi 1.5 34B achieves approximately 3.8 tokens per second decode speed with a time-to-first-token of 51346ms using Q4_K_M quantization.

Can RX 6800 XT 16GB run Yi 1.5 34B for coding?

For coding workloads, Yi 1.5 34B on RX 6800 XT 16GB receives a F grade with 3.8 tok/s and 4K context.

What context window can Yi 1.5 34B use on RX 6800 XT 16GB?

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

What should I upgrade first if Yi 1.5 34B feels slow on RX 6800 XT 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 XT 16GB See all hardware for Yi 1.5 34B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/yi-1.5-34b-on-rx-6800-xt-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: