Raises estimated decode speed by about 931%.
Adds memory headroom for longer context windows and future model growth.
~$1,999 MSRP
Aya Expanse 32B needs ~25.3 GB VRAM. NVIDIA L4 24GB has 24.0 GB. With Q4_K_M quantization, expect ~4 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
1.3 GB over capacity — needs offload or smaller quantization
Fit status
Runs with offload (needs ~1 GB host RAM)
Decode
4.2 tok/s
TTFT
45948 ms
Safe context
8K
Memory
25.3 GB / 24.0 GB
This model fits, but memory bandwidth is the part holding decode speed back.
Throughput will feel slow
Estimated decode speed is only 4.2 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.
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.
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs with offload (needs ~0 GB host RAM) | 4.7 tok/s | 22581 ms | 8K |
| Coding | C | Runs with offload (needs ~1 GB host RAM) | 4.2 tok/s | 45948 ms | 8K |
| Agentic Coding | D | Very compromised (needs ~2.6 GB host RAM) | 3.5 tok/s | 81158 ms | 8K |
| Reasoning | C | Runs with offload (needs ~1 GB host RAM) | 4.2 tok/s | 54302 ms | 8K |
| RAG | D | Very compromised (needs ~2.6 GB host RAM) | 3.5 tok/s | 101448 ms | 8K |
How Aya Expanse 32B (32B params) fits at each quantization level on NVIDIA L4 24GB (24.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 12.5 GB | Low | B56 |
Q3_K_S | 3 | 15.7 GB | Low | B55 |
NVFP4Best for your GPU | 4 | 17.9 GB | Medium | C55 |
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 |
Copy-paste commands to run Aya Expanse 32B on your machine.
Run
ollama run aya-expanse:32b升级选项
Raises estimated decode speed by about 931%.
Adds memory headroom for longer context windows and future model growth.
~$1,999 MSRP
Raises estimated decode speed by about 898%.
Adds memory headroom for longer context windows and future model growth.
~$2,499 MSRP
Raises estimated decode speed by about 512%.
Adds memory headroom for longer context windows and future model growth.
~$4,000 MSRP
Yes, NVIDIA L4 24GB can run Aya Expanse 32B with a C grade (Runs with offload (needs ~1 GB host RAM)). Expected decode speed: 4.2 tok/s.
Aya Expanse 32B (32B parameters) requires approximately 25.3 GB of memory with Q4_K_M quantization.
The recommended quantization for Aya Expanse 32B is Q4_K_M, which balances quality and memory efficiency.
On NVIDIA L4 24GB, Aya Expanse 32B achieves approximately 4.2 tokens per second decode speed with a time-to-first-token of 45948ms using Q4_K_M quantization.
For coding workloads, Aya Expanse 32B on NVIDIA L4 24GB receives a C grade with 4.2 tok/s and 8K context.
On NVIDIA L4 24GB, Aya Expanse 32B can safely use up to 8K tokens of context. The model's official context limit is 8K, but available memory constrains the safe maximum.
Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/aya-expanse-32b-on-l4-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: