Qwen3.5-35B-A3B (MoE) on NVIDIA GeForce RTX 5080 16GB: VRAM Requirement & Speed Estimate
A single RTX 5080 (15.7 GB usable VRAM) cannot fully fit Qwen3.5-35B-A3B (MoE) at Q4_K_M (23.34 GB required). Consider multi-GPU tensor parallelism, a smaller parameter variant, or cloud GPU / API deployment.
Physical 16 GB · Load 148.9%
MoE: reads only 1.82 GB active weights/step
Enable Q8/Q4 KV quantization to scale batch concurrency
OLLAMA_CONTEXT_LENGTH=16384 ollama run qwen3.5:35b-a3bInsufficient Local VRAM? Ways to Run Qwen3.5-35B-A3B (MoE)
Rent an hourly high-VRAM cloud GPU pod, or check the 12-month Buy vs Cloud vs API break-even curve.
📊 All Quantization Levels for Qwen3.5-35B-A3B (MoE) on RTX 5080
| Quantization | Total VRAM (16K) | Verdict | Est. Speed | Max Context |
|---|---|---|---|---|
| FP16 / BF16 | 73.1 GB | Out of VRAM (OOM) | — | — |
| FP8 / Q8_0 | 39.63 GB | Out of VRAM (OOM) | — | — |
| GGUF Q6_K | 30.98 GB | Out of VRAM (OOM) | — | — |
| GGUF Q5_K_M | 27.09 GB | Out of VRAM (OOM) | — | — |
| Q4_K_M / AWQ | 23.34 GB | Partial RAM Offload (Slow) | ~85.4 tok/s | — |
| GGUF IQ4_XS | 20.67 GB | Partial RAM Offload (Slow) | ~119.9 tok/s | — |
| GGUF Q3_K_M | 19.15 GB | Partial RAM Offload (Slow) | ~155.8 tok/s | — |
| GGUF Q2_K | 15.76 GB | Partial RAM Offload (Slow) | ~420 tok/s | 12K |
💡 Recommended Alternative GPUs & Macs for Qwen3.5-35B-A3B (MoE)
Frequently Asked Questions
Can NVIDIA GeForce RTX 5080 16GB run Qwen3.5-35B-A3B (MoE) locally?
A single RTX 5080 (15.7 GB usable VRAM) cannot fully fit Qwen3.5-35B-A3B (MoE) at Q4_K_M (23.34 GB required). Consider multi-GPU tensor parallelism, a smaller parameter variant, or cloud GPU / API deployment.
What is the best quantization for Qwen3.5-35B-A3B (MoE) on RTX 5080?
Qwen3.5-35B-A3B (MoE) (35B parameters) exceeds single-device VRAM even at aggressive 2–3 bit quantization. Cloud GPUs or hosted APIs are recommended.
How much VRAM does Qwen3.5-35B-A3B (MoE) need in full FP16 precision?
In unquantized FP16/BF16 precision (16K context), Qwen3.5-35B-A3B (MoE) requires 73.1 GB VRAM (70 GB for weights alone). Because it uses a Mixture-of-Experts (MoE) architecture, all 35B parameters must sit in memory, while only 3B active parameters are read per token.