llmrun
tvall43Qwen 3.5Qwen3_5MoeForConditionalGeneration

Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap — Hardware Requirements & GPU Compatibility

ChatReasoning

Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap is a 14.1B-parameter open language model from tvall43 in the Qwen 3.5 family. It supports a context window of up to 262,144 tokens. At Q4_K_M it needs about 8.87 GB of VRAM — see which GPUs and Macs can run it below.

14.1B params · MoE3.4B active262K contextApache 2.0147 downloads5 likes7.4K quant downloads
S

Runs great on a 24 GB GPU

Runs from8 GB Q3_K_M · 64KBest on24 GB Q4_K_M · ~182 tok/s · 256KMacs from16 GB Q4_K_M · ~43 tok/s

Apache 2.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Recommended

Ollama
one command · needs Ollama installed
$ollama run hf.co/tvall43/Qwen3.5-14B-A3B-Claude-4.6-Opus-Reasoning-Distilled-reap-gguf

Q4_K_M fits fully on the RTX 4090 · 15.0 GB free · 16K context

install, OS, other quants

Other ways

each opens step-by-step

Run in cloud

Fits on RTX 3060 12GB (3 GB headroom) · Q4_K_M

Generation speed
~88 tok/s
generation speed
Cost per 1M output tokens
$0.24
per 1M output tokens

How Much VRAM Does Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
6.4 GB6.6 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 256K context · ~219 tok/s
7.3 GB7.5 GB3-bit medium — 3-bit medium quantizationFits: 256K context · ~204 tok/s
8.9 GB9.1 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 256K context · ~182 tok/s
10.5 GB10.7 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 256K context · ~164 tok/s
12.1 GB12.3 GB6-bit, very good — 6-bit quantization, very good qualityFits: 256K context · ~150 tok/s
14.5 GB14.8 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 256K context · ~132 tok/s
28.7 GB28.9 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingDoes not fit: needs 28.7 GB
est.calculated, no published file yet

Selected Q4_K_M

4-bit medium quantization

9.0GBat 16K context

Weights
8.5 GB
KV cache
0.2 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 15.1 GB free · ~182 tok/s

≥50 tok/s needs ≥186 GB/s · RTX 5090 ~247, RTX 3090 Ti ~182

Which Hardware Can Run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

Q4_K_M · 8.9 GB

Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap (Q4_K_M) requires 8.9 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 12+ GB is recommended. Using the full 262K context window can add up to 2.6 GB, bringing total usage to 11.5 GB. 40 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti, NVIDIA GeForce RTX 3080 Ti. 150 devices with unified memory can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB), Mac Mini M2 Pro (16 GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8 GB · RTX 4060Q3_K_M · 7.4 GB · ~82 tok/s · 64K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 9 GB · ~88 tok/s · 256K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 9 GB · ~104 tok/s · 256K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 9 GB · ~182 tok/s · 256K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 9 GB · ~30 tok/s · 256KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 9 GB · ~73 tok/s · 256KMacs →

Alternatives to Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap

Qwen 3.5 family · 34 models →

Similar models

6
ModelScoreVRAMtok/sWhy it is similar
Apriel 1.6 15B ThinkerServiceNow-AI—13.2 GB~67same size
Phi 4 ReasoningMicrosoft—12.5 GB~69same size
Phi 3 Medium 128k InstructMicrosoft—12 GB~72same size
Qwen1.5 14BAlibaba—22.2 GB~63same size
JiRackUltra 14BCMSManhattan—12.4 GB~69same size
Nemotron Terminal 14BNVIDIA—11.9 GB~69same size

Specifications

Publisher
tvall43
Family
Qwen 3.5
Parameters
14.1B
Active parameters
3.4B per token
Architecture
Qwen3_5MoeForConditionalGeneration
Context Length
262,144 tokens
Vocabulary Size
248,320
Release Date
2026-03-09
License
Apache 2.0

Frequently Asked Questions

How much VRAM does Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap need?

Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap requires 8.9 GB of VRAM at Q4_K_M, or 28.7 GB at BF16. Full 262K context adds up to 2.6 GB (11.5 GB total).

VRAM = Weights + KV Cache + Overhead

Weights = 14.1B × 4.8 bits ÷ 8 = 8.5 GB

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

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

KV Cache + Overhead ≈ 3 GB (at full 262K context)

VRAM usage by quantization

8.9 GB
11.5 GB

Learn more about VRAM estimation →

Can NVIDIA GeForce RTX 4090 run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

Yes, at Q8_0 (14.5 GB) or lower. Higher quantizations like BF16 (28.7 GB) exceed the NVIDIA GeForce RTX 4090's 24 GB.

What's the best quantization for Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

For Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap, Q4_K_M (8.9 GB) offers the best balance of quality and VRAM usage. Q5_K_M (10.5 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 6.4 GB.

VRAM requirement by quantization

Q2_K
6.4 GB
Q4_K_M ★
8.9 GB
Q5_K_M
10.5 GB
Q6_K
12.1 GB
Q8_0
14.5 GB
BF16
28.7 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap on a Mac?

Yes — Mac Mini M2 Pro (16 GB) and 133 other Macs can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 8.9 GB of usable unified memory (RAM minus macOS overhead).

Can I run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap locally?

Yes — Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

At Q4_K_M, Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap can reach ~118 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~182 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = 1000 ÷ (active GB ÷ (bandwidth GB/s × efficiency) × 1000 + layers × routing ms)

Mixture-of-Experts: just the active experts get read for each token, along with a fixed routing cost per layer.

Example: NVIDIA B200 → 2.2 GB active ÷ (8000 × 0.65) = 0.42 ms, plus 40 layers × 0.055 ms = 2.20 ms, so 1000 ÷ 2.62 ms = ~382 tok/s

Estimated speed at Q4_K_M (8.9 GB)

~382 tok/s
~182 tok/s
~382 tok/s
~348 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 Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

At Q4_K_M, the download is about 8.48 GB. The full-precision BF16 version is 28.27 GB. The smallest option (Q2_K) is 6.01 GB.

Which GPUs can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

40 consumer GPUs can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap at Q4_K_M. Top options include AMD Radeon RX 6800, AMD Radeon RX 6800 XT, AMD Radeon RX 6900 XT, AMD Radeon RX 6700 XT. 26 GPUs have plenty of headroom for comfortable inference.

Which devices can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap?

150 devices with unified memory can run Qwen3.5 14B A3B Claude 4.6 Opus Reasoning Distilled Reap at Q4_K_M (8.9 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.