Can I run Qwen3-Coder-Next on an RTX 5060 Ti 16GB?
With --n-cpu-moe 35: the Q4_K_M GGUF keeps 15.3 GB on the RTX 5060 Ti and 31.6 GB in system RAM, with the experts of 35 of its 48 layers moved there. Whole, Qwen3-Coder-Next needs about 50.7 GB at Q4_K_M with 32K tokens of context, 34.7 GB more than the RTX 5060 Ti 16GB holds. The smallest setup here that holds Qwen3-Coder-Next at Q4_K_M with 32K is 2× RTX 5090 (64 GB).
With offload the Q4_K_M GGUF with --n-cpu-moe 35 and 32K tokens of context
- On the card
- 15.3 GB
- RTX 5060 Ti
- 16 GB, 448 GB/s
- In RAM
- 31.6 GB
- Tokens/s
- 22–37 tokens/s
With the Q4_K_M GGUF, --n-cpu-moe 35 and 32K tokens of context it writes about 22–37 tokens/s for one request on an RTX 5060 Ti 16GB and dual-channel DDR5-5600.
Qwen3-Coder-Next on the RTX 5060 Ti as the context fills
One request, FP16 KV cache, 0.5 GB plus 10% overhead; a minus sign is memory missing, and tight is less than 0.5 GB free.
| Context | Q4_K_M | Free | Tokens/s | Q8_0 | Free | Tokens/s |
|---|---|---|---|---|---|---|
| 4K | 50.0 GB | −34.0 GB | — | 87.3 GB | −71.3 GB | — |
| 8K | 50.1 GB | −34.1 GB | — | 87.4 GB | −71.4 GB | — |
| 16K | 50.3 GB | −34.3 GB | — | 87.6 GB | −71.6 GB | — |
| 32K | 50.7 GB | −34.7 GB | — | 88.0 GB | −72.0 GB | — |
| 64K | 51.5 GB | −35.5 GB | — | 88.9 GB | −72.9 GB | — |
| 128K | 53.2 GB | −37.2 GB | — | 90.5 GB | −74.5 GB | — |
| 256K (full) | 56.5 GB | −40.5 GB | — | 93.8 GB | −77.8 GB | — |
--n-cpu-moe for Qwen3-Coder-Next on the RTX 5060 Ti
With --n-cpu-moe 35 the Q4_K_M GGUF keeps 15.3 GB on the RTX 5060 Ti and 31.6 GB in RAM, about 22–37 tokens/s with DDR5-5600. Measured Q4_K_M file, 1 GB of buffers; tokens/s by system RAM speed.
Qwen3-Coder-Next on more than one RTX 5060 Ti
| Cards | Best at 32K | Tokens/s | Q4_K_M longest | Q4_K_M tokens/s |
|---|---|---|---|---|
| 2× (32 GB) | Nothing fits | — | Does not fit | — |
| 4× (64 GB) | Q5_K_M | 112–219 | 256K (full) | 119–237 |
Tensor parallel with the combined bandwidth, as in vLLM; llama.cpp splits layers by default and runs at about one card's speed.
Other options
- The next smaller setting, Q3_K_M, takes 41.2 GB at 32K, 25.2 GB over the RTX 5060 Ti; it does not fit with 0.5 GB to spare even with 1K tokens.
- Smallest setup for Q4_K_M at 32K: 2× RTX 5090 (64 GB).
Run Qwen3-Coder-Next on the RTX 5060 Ti with llama-server
llama-server -hf unsloth/Qwen3-Coder-Next-GGUF:Q4_K_M -c 32768 --n-cpu-moe 35Qwen3-Coder-Next-Q4_K_M.gguf, 48.5 GB, from unsloth/
Questions
Can I run Qwen3-Coder-Next on an RTX 5060 Ti 16GB?
With --n-cpu-moe 35: the Q4_K_M GGUF keeps 15.3 GB on the RTX 5060 Ti and 31.6 GB in system RAM, with the experts of 35 of its 48 layers moved there. Whole, Qwen3-Coder-Next needs about 50.7 GB at Q4_K_M with 32K tokens of context, 34.7 GB more than the RTX 5060 Ti 16GB holds. The smallest setup here that holds Qwen3-Coder-Next at Q4_K_M with 32K is 2× RTX 5090 (64 GB).
How fast is Qwen3-Coder-Next on an RTX 5060 Ti 16GB?
With the Q4_K_M GGUF, --n-cpu-moe 35 and 32K tokens of context it writes about 22–37 tokens/s for one request on an RTX 5060 Ti 16GB and dual-channel DDR5-5600.
Does Qwen3-Coder-Next need --n-cpu-moe on an RTX 5060 Ti 16GB?
With --n-cpu-moe 35 the Q4_K_M GGUF keeps 15.3 GB on the RTX 5060 Ti and 31.6 GB in RAM, about 22–37 tokens/s with DDR5-5600.
What does a second RTX 5060 Ti 16GB change for Qwen3-Coder-Next?
Even two RTX 5060 Ti 16GB cards (32 GB) do not hold Qwen3-Coder-Next at 32K.
Try other settings in the VRAM calculator, the speed calculator or the MoE offload planner. See also Qwen3-Coder-Next VRAM requirements, what LLMs an RTX 5060 Ti 16GB can run and every pair, or detect your own GPU. Model data checked .