CanRun

Can I run Gemma 4 26B-A4B on the GeForce RTX 5060 Ti 16GB?

Runs wellQ4_K_M keeps attention and the experts of 24 layers on the GPU (15.4 GB) and the remaining experts in 2.9 GB of system RAM: Runs well, est. 59.2 tok/s (41.4–76.9, theoretical estimate ±30%).

16 GB VRAM · 448.0 GB/s · FP16 23.7 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.

Every quant of Gemma 4 26B-A4B on the GeForce RTX 5060 Ti 16GB

4 tracked GGUF files, smallest first, at 32 GB of system RAM and 8k context
QuantFile sizeVerdictSpeedMemoryRuns asNotes
UD-Q2_K_XL10.55 GBRuns great
est. 101.4 tok/s81.1–121.7calibrated estimate ±20%
11.9 / 16.0 GBFull GPU—
IQ4_XS13.60 GBRuns great
est. 78.1 tok/s62.5–93.7calibrated estimate ±20%
14.9 / 16.0 GBFull GPU—
Q4_K_Mbaseline16.95 GBRuns well
est. 59.2 tok/s41.4–76.9theoretical estimate ±30%
15.4 / 16.0 GB + 2.9 GB RAMMoE experts in RAMNot fully on the GPU — Runs great needs the whole model in GPU memory
Q8_026.86 GBRuns well
est. 31.4 tok/s21.9–40.8theoretical estimate ±30%
14.4 / 16.0 GB + 13.8 GB RAMMoE experts in RAMNot fully on the GPU — Runs great needs the whole model in GPU memory

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
14.1 GB
KV cache
0.2 GB
Compute buffer
0.6 GB
OS reserve
0.6 GB
Free
0.6 GB
Weights in system RAM
2.9 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
17.6 GBRuns well
est. 60.1 tok/s42.1–78.2theoretical estimate ±30%
17.5 GBRuns well
est. 60.6 tok/s42.4–78.7theoretical estimate ±30%
17.5 GBRuns well
est. 60.8 tok/s42.6–79.1theoretical estimate ±30%
8k
17.7 GBRuns well
est. 59.2 tok/s41.4–76.9theoretical estimate ±30%
17.6 GBRuns well
est. 60.0 tok/s42.0–78.1theoretical estimate ±30%
17.6 GBRuns well
est. 60.5 tok/s42.4–78.7theoretical estimate ±30%
16k
17.9 GBRuns well
est. 55.5 tok/s38.9–72.2theoretical estimate ±30%
17.8 GBRuns well
est. 59.0 tok/s41.3–76.7theoretical estimate ±30%
17.7 GBRuns well
est. 60.0 tok/s42.0–78.0theoretical estimate ±30%
32k
18.4 GBRuns well
est. 50.9 tok/s35.6–66.2theoretical estimate ±30%
18.1 GBRuns well
est. 55.3 tok/s38.7–71.9theoretical estimate ±30%
17.9 GBRuns well
est. 57.0 tok/s39.9–74.1theoretical estimate ±30%
64k
19.4 GBRuns well
est. 43.6 tok/s30.5–56.7theoretical estimate ±30%
18.7 GBRuns well
est. 50.5 tok/s35.4–65.7theoretical estimate ±30%
18.4 GBRuns well
est. 53.4 tok/s37.4–69.4theoretical estimate ±30%
128k
21.3 GBRuns well
est. 33.9 tok/s23.7–44.1theoretical estimate ±30%
20.1 GBRuns well
est. 42.0 tok/s29.4–54.6theoretical estimate ±30%
19.4 GBRuns well
est. 47.4 tok/s33.2–61.6theoretical estimate ±30%
256k
25.2 GBRuns slowly
est. 23.5 tok/s16.4–30.5theoretical estimate ±30%
22.7 GBRuns well
est. 31.4 tok/s22.0–40.9theoretical estimate ±30%
21.4 GBRuns well
est. 38.7 tok/s27.1–50.3theoretical estimate ±30%

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

At Q4_K_M the verdict stays Runs well up to 128k context with an f16 KV cache, and up to 256k with q8_0.

Estimated speed

Generation
est. 59.2 tok/s (41.4–76.9, theoretical estimate ±30%)
Prompt processing
Prompt-processing estimates only apply when the whole model runs on the GPU.

Why this verdict: Not fully on the GPU — Runs great needs the whole model in GPU memory

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 UD-Q4_K_M file. Both tools download from Hugging Face on first run.

File: gemma-4-26B-A4B-it-UD-Q4_K_M.gguf (16.95 GB) from unsloth/gemma-4-26B-A4B-it-GGUF.

llama.cpp
llama-server -hf unsloth/gemma-4-26B-A4B-it-GGUF:UD-Q4_K_M -c 8192 -ngl all --n-cpu-moe 6 -fa on
  • -ngl all loads every layer on the GPU.
  • --n-cpu-moe 6 keeps the experts in the first 6 layers in system RAM; the remaining 24 layers with experts keep them on the GPU. This estimate assumes the same split.
  • If loading fails with an out-of-memory error, raise the value to 7, or to 8 if that isn't enough.
  • llama.cpp b7410 (December 2025) and later split the model in a similar way on their own if you leave out -ngl and --n-cpu-moe.
  • -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.09 GB at 8k context.
Ollama

PowerShell (quit the Ollama tray app first):

$env:OLLAMA_CONTEXT_LENGTH="8192"; ollama serve
ollama run hf.co/unsloth/gemma-4-26B-A4B-it-GGUF:UD-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 0.30 and later automatically keep part of the experts in system RAM to fit your VRAM. Older versions split whole layers instead, which is much slower.
  • /set parameter num_ctx 8192

Related pages

Frequently asked questions

Can I run Gemma 4 26B-A4B on the GeForce RTX 5060 Ti 16GB?

Q4_K_M keeps attention and the experts of 24 layers on the GPU (15.4 GB) and the remaining experts in 2.9 GB of system RAM: Runs well, est. 59.2 tok/s (41.4–76.9, theoretical estimate ±30%). Q4_K_M needs 17.7 GB at 8k context; this setup has 15.4 GB of usable memory and 28.0 GB of free system RAM.

How much context can Gemma 4 26B-A4B use on the GeForce RTX 5060 Ti 16GB?

At Q4_K_M the verdict stays Runs well up to 128k context with an f16 KV cache (2.7 GB of KV) and up to 256k with a q8_0 KV cache (2.9 GB). The model supports up to 256k.

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

Q4_K_M (16.95 GB) is the recommended balance: Runs well, est. 59.2 tok/s (41.4–76.9, theoretical estimate ±30%). The largest tracked file that still gets Runs well is Q8_0 (26.86 GB), est. 31.4 tok/s (21.9–40.8, theoretical estimate ±30%).

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.