Aya Expanse 8B needs ~8.5 GB VRAM. RTX 5060 8GB has 8.0 GB. With Q4_K_M quantization, expect ~38 tok/s.
Operating mode
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.
Select quantization to explore
0.5 GB over capacity — needs offload or smaller quantization
Fit status
Runs with offload (needs ~0.3 GB host RAM)
Decode
40.4 tok/s
TTFT
4797 ms
Safe context
8K
Memory
8.5 GB / 8.0 GB
Offload
10%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% 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.
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 {ram} GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Tight fit | 60.2 tok/s | 1754 ms | 8K |
| Coding | C | Runs with offload | 37.5 tok/s | 5157 ms | 8K |
| Agentic Coding | F | Too heavy | 26.5 tok/s | 10624 ms | 8K |
| Reasoning | C | Runs with offload (needs ~0.3 GB host RAM) | 40.4 tok/s | 5669 ms | 8K |
| RAG | F | Too heavy | 26.5 tok/s | 13280 ms | 8K |
How Aya Expanse 8B (8B params) fits at each quantization level on RTX 5060 8GB (8.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 3.1 GB | Low | B55 |
Q3_K_S | 3 | 3.9 GB | Low | C55 |
NVFP4 | 4 |
Copy-paste commands to run Aya Expanse 8B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "CohereForAI/aya-expanse-8b" \
--hf-file "aya-expanse-8b-Q4_K_M.gguf" \
-c 4096 -ngl 99Upgrade options
RTX 3060 12GBBudget pickRemoves host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$329 MSRP
RTX 5060 Ti 16GBBest valueRemoves host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 51%.
~$449 MSRP
RTX 4060 Ti 16GBNVIDIA upgradeRemoves host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$499 MSRP
Yes, RTX 5060 8GB can run Aya Expanse 8B with a C grade (Runs with offload). Expected decode speed: 37.5 tok/s.
Aya Expanse 8B (8B parameters) requires approximately 8.5 GB of memory with Q4_K_M quantization.
The recommended quantization for Aya Expanse 8B is Q4_K_M, which balances quality and memory efficiency.
On RTX 5060 8GB, Aya Expanse 8B achieves approximately 37.5 tokens per second decode speed with a time-to-first-token of 5157ms using Q4_K_M quantization.
For coding workloads, Aya Expanse 8B on RTX 5060 8GB receives a C grade with 37.5 tok/s and 8K context.
On RTX 5060 8GB, Aya Expanse 8B can safely use up to 8K tokens of context. The model's official context limit is 8K, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/aya-expanse-8b-on-rtx-5060-8gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| Medium |
| C55 |
Q4_K_MBest for your GPU | 4 | 4.9 GB | Medium | C54 |
Q5_K_M | 5 | 5.8 GB | High | F0 |
Q6_K | 6 | 6.6 GB | High | F0 |
Q8_0 | 8 | 8.6 GB | Very High | F0 |
F16 | 16 | 16.4 GB | Maximum | F0 |
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.