Adds memory headroom for longer context windows and future model growth.
~$6,999 MSRP
![]() |
VOOZH | about |
Gemma 3 4B needs ~24.5 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~29 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
Fit status
Runs well
Decode
56.0 tok/s
TTFT
3457 ms
Safe context
128K
Memory
18.8 GB / 108.8 GB
This setup is broadly balanced for this model.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 12.1 tok/s | 8739 ms | 4K |
| Coding | F | Too heavy | 12.1 tok/s | 16022 ms | 4K |
| Agentic Coding | F | Too heavy | 12.1 tok/s | 23304 ms | 4K |
| Reasoning | F | Too heavy | 12.1 tok/s | 18935 ms | 4K |
| RAG | F | Too heavy | 12.1 tok/s | 29130 ms | 4K |
How Gemma 3 4B (4B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 1.6 GB | Low | B60 |
Q3_K_S | 3 | 2.0 GB | Low | B60 |
NVFP4 | 4 |
Copy-paste commands to run Gemma 3 4B on your machine.
Run
ollama run gemma3:4bUpgrade options
2.2 GB |
| Medium |
| B60 |
Q4_K_M | 4 | 2.4 GB | Medium | B60 |
Q5_K_M | 5 | 2.9 GB | High | B60 |
Q6_K | 6 | 3.3 GB | High | B60 |
Q8_0 | 8 | 4.3 GB | Very High | B60 |
F16Best for your GPU | 16 | 8.2 GB | Maximum | B61 |
Not always. NVIDIA DGX Spark 128GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.