Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$999 MSRP
Aya Expanse 32B needs ~23.3 GB VRAM. RX 7900 XT 20GB has 20.0 GB. With NVFP4 quantization, expect ~17 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
4.9 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
12.7 tok/s
TTFT
15260 ms
Safe context
4K
Memory
24.9 GB / 20.0 GB
Offload
20%
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 2.5 GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | D | Very compromised (needs ~3 GB host RAM) | 14.1 tok/s | 7487 ms | 4K |
| Coding | F | Too heavy | 11.7 tok/s | 16596 ms | 4K |
| Agentic Coding | F | Too heavy | 10.4 tok/s | 27035 ms | 4K |
| Reasoning | F | Too heavy | 12.7 tok/s | 18035 ms | 4K |
| RAG | F | Too heavy | 10.4 tok/s | 33794 ms | 4K |
How Aya Expanse 32B (32B params) fits at each quantization level on RX 7900 XT 20GB (20.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_KBest for your GPU | 2 | 12.5 GB | Low | B56 |
Q3_K_S | 3 | 15.7 GB | Low | F0 |
Copy-paste commands to run Aya Expanse 32B on your machine.
Run
ollama run aya-expanse:32bUpgrade options
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$999 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$1,899 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$2,249 MSRP
Yes, RX 7900 XT 20GB can run Aya Expanse 32B at NVFP4 quantization (Very compromised (needs ~2.5 GB host RAM)). The recommended Q4_K_M requires 24.9 GB which exceeds available memory, but at NVFP4 it needs only 23.3 GB. Expected decode speed: 16.7 tok/s.
Aya Expanse 32B (32B parameters) requires approximately 24.9 GB at Q4_K_M quantization. On RX 7900 XT 20GB, it fits at NVFP4 using 23.3 GB.
The recommended quantization is Q4_K_M, but on RX 7900 XT 20GB the best fitting quantization is NVFP4, which uses 23.3 GB.
On RX 7900 XT 20GB, Aya Expanse 32B achieves approximately 16.7 tokens per second decode speed with a time-to-first-token of 11599ms using NVFP4 quantization.
For coding workloads, Aya Expanse 32B on RX 7900 XT 20GB receives a F grade with 11.7 tok/s and 4K context.
On RX 7900 XT 20GB, Aya Expanse 32B can safely use up to 4K tokens of context at NVFP4 quantization. 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-32b-on-rx-7900-xt-20gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 4 |
17.9 GB |
| Medium |
| F0 |
Q4_K_M | 4 | 19.5 GB | Medium | F0 |
Q5_K_M | 5 | 23.0 GB | High | F0 |
Q6_K | 6 | 26.2 GB | High | F0 |
Q8_0 | 8 | 34.2 GB | Very High | F0 |
F16 | 16 | 65.6 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.