second-state·Yi 1.5·LlamaForCausalLM

Yi 1.5 34B Chat GGUF — Hardware Requirements & GPU Compatibility

Chat
79 downloads 4 likes4K context

Specifications

Publisher
second-state
Family
Yi 1.5
Parameters
34B
Architecture
LlamaForCausalLM
Context Length
4,096 tokens
Vocabulary Size
64,000
License
Apache 2.0

Get Started

How Much VRAM Does Yi 1.5 34B Chat GGUF Need?

Select a quantization to see compatible GPUs below.

QuantizationBitsVRAM
Q2_K3.4015.3 GB
Q3_K_S3.5015.7 GB
Q3_K_M3.9017.4 GB
Q4_04.0017.8 GB
Q4_K_M4.8021.2 GB
Q5_K_M5.7025.0 GB
Q6_K6.6028.9 GB
Q8_08.0034.8 GB

Which GPUs Can Run Yi 1.5 34B Chat GGUF?

Q4_K_M · 21.2 GB

Yi 1.5 34B Chat GGUF (Q4_K_M) requires 21.2 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 28+ GB is recommended. Using the full 4K context window can add up to 0.5 GB, bringing total usage to 21.7 GB. 5 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti.

Which Devices Can Run Yi 1.5 34B Chat GGUF?

Q4_K_M · 21.2 GB

21 devices with unified memory can run Yi 1.5 34B Chat GGUF, including NVIDIA DGX H100, NVIDIA DGX A100 640GB, Mac Mini M4 Pro (24 GB).

Related Models

Frequently Asked Questions

How much VRAM does Yi 1.5 34B Chat GGUF need?

Yi 1.5 34B Chat GGUF requires 21.2 GB of VRAM at Q4_K_M, or 34.8 GB at Q8_0. Full 4K context adds up to 0.5 GB (21.7 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 34B × 4.8 bits ÷ 8 = 20.4 GB

KV Cache + Overhead 0.8 GB (at 2K context + ~0.3 GB framework)

KV Cache + Overhead 1.3 GB (at full 4K context)

VRAM usage by quantization

21.2 GB
21.7 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 4090 run Yi 1.5 34B Chat GGUF?

Yes, at Q5_0 (22.1 GB) or lower. Higher quantizations like Q5_K_S (24.2 GB) exceed the NVIDIA GeForce RTX 4090's 24 GB.

What's the best quantization for Yi 1.5 34B Chat GGUF?

For Yi 1.5 34B Chat GGUF, Q4_K_M (21.2 GB) offers the best balance of quality and VRAM usage. Q5_0 (22.1 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 15.3 GB.

VRAM requirement by quantization

Q2_K
15.3 GB
Q4_0
17.8 GB
Q4_K_M
21.2 GB
Q5_0
22.1 GB
Q5_K_S
24.2 GB
Q8_0
34.8 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Yi 1.5 34B Chat GGUF on a Mac?

Yi 1.5 34B Chat GGUF requires at least 15.3 GB at Q2_K, which exceeds the unified memory of most consumer Macs. You would need a Mac Studio or Mac Pro with a high-memory configuration.

Can I run Yi 1.5 34B Chat GGUF locally?

Yes — Yi 1.5 34B Chat GGUF can run locally on consumer hardware. At Q4_K_M quantization it needs 21.2 GB of VRAM. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Yi 1.5 34B Chat GGUF?

At Q4_K_M, Yi 1.5 34B Chat GGUF can reach ~138 tok/s on AMD Instinct MI300X. On NVIDIA GeForce RTX 4090: ~31 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: AMD Instinct MI300X5300 ÷ 21.2 × 0.55 = ~138 tok/s

Estimated speed at Q4_K_M (21.2 GB)

~138 tok/s
~31 tok/s
~103 tok/s
~85 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of Yi 1.5 34B Chat GGUF?

At Q4_K_M, the download is about 20.40 GB. The full-precision Q8_0 version is 34.00 GB. The smallest option (Q2_K) is 14.45 GB.

Which GPUs can run Yi 1.5 34B Chat GGUF?

5 consumer GPUs can run Yi 1.5 34B Chat GGUF at Q4_K_M (21.2 GB). Top options include NVIDIA GeForce RTX 5090, AMD Radeon RX 7900 XTX, NVIDIA GeForce RTX 3090. 1 GPU have plenty of headroom for comfortable inference.

Which devices can run Yi 1.5 34B Chat GGUF?

21 devices with unified memory can run Yi 1.5 34B Chat GGUF at Q4_K_M (21.2 GB), including Mac Mini M4 (32 GB), Mac Mini M4 Pro (24 GB), Mac Mini M4 Pro (48 GB), Mac Pro M2 Ultra (192 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.