CanRun

Can I run Qwen3.5 27B on the GeForce RTX 5070?

Runs slowlyQ4_K_M does not fit fully in VRAM, so 6.8 GB of the weights run from system RAM: Runs slowly, est. 5.6 tok/s (4.5–6.7, calibrated estimate ±20%).

12 GB VRAM · 672.0 GB/s · FP16 30.9 TFLOPS. Assumes 32 GB of DDR5-5600 system RAM, Windows with this GPU driving the display, 8k context and an f16 KV cache. The verdict and quant file above stay the same anywhere from 16 to 128 GB of system RAM. The GeForce RTX 5070 Ti Laptop has the same memory setup (12 GB, 672.0 GB/s), so its generation-speed estimate is the same; only prompt processing differs.

Every quant of Qwen3.5 27B on the GeForce RTX 5070

4 tracked GGUF files, smallest first, at 32 GB of system RAM and 8k context
QuantFile sizeVerdictSpeedMemoryRuns asNotes
UD-Q2_K_XL12.04 GBRuns slowly
est. 15.7 tok/s12.6–18.8calibrated estimate ±20%
12.0 / 12.0 GB + 1.8 GB RAMPartial offloadLess than 90% on the GPU — a GPU/CPU split is capped at Runs slowly
IQ4_XS15.71 GBRuns slowly
est. 6.8 tok/s5.4–8.1calibrated estimate ±20%
12.0 / 12.0 GB + 5.4 GB RAMPartial offload—
Q4_K_Mbaseline17.11 GBRuns slowly
est. 5.6 tok/s4.5–6.7calibrated estimate ±20%
12.0 / 12.0 GB + 6.8 GB RAMPartial offload—
Q8_029.05 GBWon't run
est. 2.2 tok/s1.8–2.7calibrated estimate ±20%
12.0 / 12.0 GB + 18.8 GB RAMPartial offloadFits, but too slow to use

Models with a thinking mode spend extra tokens thinking, so their speed thresholds are 1.5× stricter (30 / 12 / 3 tok/s). With thinking turned off, a model may do one grade better.

Where the memory goes at Q4_K_M

Weights, KV cache and compute buffer are the model; the OS reservation is the display driver.
GPU memory
System RAM
Weights
10.3 GB
KV cache
0.5 GB
Compute buffer
0.6 GB
OS reserve
0.6 GB
Weights in system RAM
6.8 GB

Context length vs. KV cache

KV cache

Memory needed and verdict at Q4_K_M for each context length and KV cache type, with estimated tokens per second.
ContextKV f16KV q8_0KV q4_0
4k
16.9 GBRuns slowly
est. 5.9 tok/s4.7–7.0calibrated estimate ±20%
16.8 GBRuns slowly
est. 6.0 tok/s4.8–7.2calibrated estimate ±20%
16.7 GBRuns slowly
est. 6.1 tok/s4.9–7.3calibrated estimate ±20%
8k
17.2 GBRuns slowly
est. 5.6 tok/s4.5–6.7calibrated estimate ±20%
17.0 GBRuns slowly
est. 5.8 tok/s4.7–7.0calibrated estimate ±20%
16.8 GBRuns slowly
est. 6.0 tok/s4.8–7.1calibrated estimate ±20%
16k
17.8 GBRuns slowly
est. 5.0 tok/s4.0–6.1calibrated estimate ±20%
17.3 GBRuns slowly
est. 5.5 tok/s4.4–6.6calibrated estimate ±20%
17.0 GBRuns slowly
est. 5.7 tok/s4.6–6.9calibrated estimate ±20%
32k
19.0 GBRuns slowly
est. 4.2 tok/s3.4–5.0calibrated estimate ±20%
18.0 GBRuns slowly
est. 4.9 tok/s3.9–5.9calibrated estimate ±20%
17.5 GBRuns slowly
est. 5.4 tok/s4.3–6.4calibrated estimate ±20%
64k
21.5 GBRuns slowly
est. 3.1 tok/s2.5–3.7calibrated estimate ±20%
19.5 GBRuns slowly
est. 4.0 tok/s3.2–4.8calibrated estimate ±20%
18.4 GBRuns slowly
est. 4.7 tok/s3.8–5.6calibrated estimate ±20%
128k
26.4 GBWon't run
est. 1.9 tok/s1.5–2.2calibrated estimate ±20%
22.4 GBWon't run
est. 2.8 tok/s2.3–3.4calibrated estimate ±20%
20.2 GBRuns slowly
est. 3.7 tok/s3.0–4.5calibrated estimate ±20%
256k
36.2 GBdoes not fit
26.3 GBWon't run
est. 1.7 tok/s1.4–2.0calibrated estimate ±20%
23.9 GBWon't run
est. 2.5 tok/s2.0–3.0calibrated estimate ±20%

S = Runs great · A = Runs well · B = Runs slowly · F = Won't run

At Q4_K_M the verdict stays Runs slowly up to 64k context with an f16 KV cache, and up to 64k with q8_0.

Estimated speed

Generation
est. 5.6 tok/s (4.5–6.7, calibrated estimate ±20%)
Prompt processing
Prompt-processing estimates only apply when the whole model runs on the GPU.

Measured on this exact combination

No public measurement for this exact combination yet; the numbers above are estimates.

If this is not enough

How to run it

Commands for the Q4_K_M file. Both tools download from Hugging Face on first run.

File: Qwen3.5-27B-Q4_K_M.gguf (17.11 GB) from unsloth/Qwen3.5-27B-MTP-GGUF.

llama.cpp
llama-server -hf unsloth/Qwen3.5-27B-MTP-GGUF:Q4_K_M -c 8192 -ngl 38 -fa on
  • -ngl 38 puts 38 of 64 layers on the GPU; if VRAM overflows, lower it by 1–2.
  • -fa on enables flash attention (needed for KV cache quantization).
  • --cache-type-k q8_0 --cache-type-v q8_0 shrinks the KV cache to 0.29 GB at 8k context.
Ollama

PowerShell (quit the Ollama tray app first):

$env:OLLAMA_CONTEXT_LENGTH="8192"; ollama serve
ollama run hf.co/unsloth/Qwen3.5-27B-MTP-GGUF:Q4_K_M
  • Ollama defaults to 4k context on GPUs under 24 GB. Set OLLAMA_CONTEXT_LENGTH when starting the server, or /set parameter num_ctx inside the chat.
  • Ollama splits layers between GPU and CPU automatically.
  • /set parameter num_ctx 8192

Related pages

Frequently asked questions

Can I run Qwen3.5 27B on the GeForce RTX 5070?

Q4_K_M does not fit fully in VRAM, so 6.8 GB of the weights run from system RAM: Runs slowly, est. 5.6 tok/s (4.5–6.7, calibrated estimate ±20%). Q4_K_M needs 17.2 GB at 8k context; this setup has 11.4 GB of usable memory and 28.0 GB of free system RAM.

How much context can Qwen3.5 27B use on the GeForce RTX 5070?

At Q4_K_M the verdict stays Runs slowly up to 64k context with an f16 KV cache (4.3 GB of KV) and up to 64k with a q8_0 KV cache (2.3 GB). The model supports up to 256k.

Which quant should I use, and how fast is it?

Q4_K_M (17.11 GB) is the recommended balance: Runs slowly, est. 5.6 tok/s (4.5–6.7, calibrated estimate ±20%). It is also the largest tracked file that gets this verdict.

Speeds are estimates from memory bandwidth, calibrated against public benchmarks, and each one comes with an error band and a confidence label. Real results vary with drivers, backend, context length and thermals.