willitrun·ai

Can Qwen 3.5 27B run on RX 6950 XT 16GB?

YES — With Q3_K_S

A74Great
Estimated from fit model

Qwen 3.5 27B needs ~18.9 GB VRAM. RX 6950 XT 16GB has 16.0 GB. With Q3_K_S quantization, expect ~13 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: MediumStack: StandardBottleneck: Host offload
Share:

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.

Qwen 3.5 27B at Q4_K_M needs 22.1 GB — too much for RX 6950 XT 16GB (16.0 GB). Runs at Q3_K_S (18.9 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 22.1 GB, exceeds 16.0 GB available
22.1 GB required16.0 GB available
138% VRAM needed

6.1 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

8.3 tok/s

TTFT

23353 ms

Safe context

4K

Memory

22.1 GB / 16.0 GB

Offload

30%

Memory breakdown

Weights16.5 GB
KV Cache3.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 feelsQwen 3.5 27B on RX 6950 XT 16GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 8.3 tok/s decode · 23.4s TTFT (warm) · 21 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 20% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 2.0 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy9.7 tok/s10892 ms4K
CodingFToo heavy8.3 tok/s23353 ms4K
Agentic CodingFToo heavy6.3 tok/s45032 ms4K
ReasoningFToo heavy8.3 tok/s27599 ms4K
RAGFToo heavy6.3 tok/s56290 ms4K

Inference speed

Qwen 3.5 27B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Qwen 3.5 27B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~79 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M78.7Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M50.2Offloads
RX 7900 XTX 24GB
24 GBQ4_K_M45.3Offloads
NVIDIARTX 3090 24GB
24 GBQ4_K_M43.0Offloads
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M36.5Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M36.1Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M36.1Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M30.4Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M28.9Fits
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M22.7Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M15.7Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M14.7Too big
MacBook Pro M1 Max 64GB
64 GBQ4_K_M14.4Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M5.2Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M3.2Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.0Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How Qwen 3.5 27B (27B params) fits at each quantization level on RX 6950 XT 16GB (16.0 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
10.5 GB
LowS93
Q3_K_S
3
13.2 GB
LowF0
NVFP4
4
15.1 GB
MediumF0
Q4_K_M
4
16.5 GB
MediumF0
Q5_K_M
5
19.4 GB
HighF0
Q6_K
6
22.1 GB
HighF0
Q8_0
8
28.9 GB
Very HighF0
F16
16
55.4 GB
MaximumF0

Get started

Copy-paste commands to run Qwen 3.5 27B on your machine.

Run

ollama run qwen3.5:27b

升级选项

能流畅运行 Qwen 3.5 27B 的硬件

Frequently asked questions

Can RX 6950 XT 16GB run Qwen 3.5 27B?

Yes, RX 6950 XT 16GB can run Qwen 3.5 27B at Q3_K_S quantization (Very compromised (needs ~2 GB host RAM)). The recommended Q4_K_M requires 22.1 GB which exceeds available memory, but at Q3_K_S it needs only 18.9 GB. Expected decode speed: 13.4 tok/s.

How much VRAM does Qwen 3.5 27B need?

Qwen 3.5 27B (27B parameters) requires approximately 22.1 GB at Q4_K_M quantization. On RX 6950 XT 16GB, it fits at Q3_K_S using 18.9 GB.

What is the best quantization for Qwen 3.5 27B?

The recommended quantization is Q4_K_M, but on RX 6950 XT 16GB the best fitting quantization is Q3_K_S, which uses 18.9 GB.

What speed will Qwen 3.5 27B run at on RX 6950 XT 16GB?

On RX 6950 XT 16GB, Qwen 3.5 27B achieves approximately 13.4 tokens per second decode speed with a time-to-first-token of 14458ms using Q3_K_S quantization.

Can RX 6950 XT 16GB run Qwen 3.5 27B for coding?

For coding workloads, Qwen 3.5 27B on RX 6950 XT 16GB receives a F grade with 8.3 tok/s and 4K context.

What context window can Qwen 3.5 27B use on RX 6950 XT 16GB?

On RX 6950 XT 16GB, Qwen 3.5 27B can safely use up to 4K tokens of context at Q3_K_S quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Qwen 3.5 27B feels slow on RX 6950 XT 16GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

See all results for RX 6950 XT 16GBSee all hardware for Qwen 3.5 27B
Embed this result

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

<iframe src="https://willitrunai.com/embed/qwen-3.5-27b-on-rx-6950-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: