Sube la velocidad estimada de decodificación alrededor de un 2355%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
Yi 34B Chat needs ~87.3 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 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
Fit status
Runs well
Decode
8.6 tok/s
TTFT
22578 ms
Safe context
200K
Memory
38.4 GB / 108.8 GB
The model fits in shared memory, but shared-memory bandwidth is now the real limiter.
Fit does not mean dedicated-VRAM speed
Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.
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.
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.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs well | 8.6 tok/s | 12315 ms | 200K |
| Coding | F | Too heavy | 2.0 tok/s | 96800 ms | 4K |
| Agentic Coding | C | Runs well | 8.6 tok/s | 32841 ms | 200K |
| Reasoning | C | Runs well | 8.6 tok/s | 26683 ms | 200K |
| RAG | C | Runs well | 8.6 tok/s | 41051 ms | 200K |
How Yi 34B Chat (34B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.3 GB | Low | C42 |
Q3_K_S | 3 | 16.7 GB | Low | C42 |
NVFP4 | 4 | 19.0 GB | Medium | C42 |
Q4_K_M | 4 | 20.7 GB | Medium | C43 |
Q5_K_M | 5 | 24.5 GB | High | C43 |
Q6_K | 6 | 27.9 GB | High | C44 |
Q8_0 | 8 | 36.4 GB | Very High | C46 |
F16Best for your GPU | 16 | 69.7 GB | Maximum | C49 |
Copy-paste commands to run Yi 34B Chat on your machine.
Run
lms load Yi-34B-Chat && lms server startOpciones de mejora
Sube la velocidad estimada de decodificación alrededor de un 2355%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
Sube la velocidad estimada de decodificación alrededor de un 2355%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
Sube la velocidad estimada de decodificación alrededor de un 3991%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
Yes, NVIDIA DGX Spark 128GB can run Yi 34B Chat at F16 quantization (Runs well). The recommended Q4_K_M requires 25.3 GB which exceeds available memory, but at F16 it needs only 87.3 GB. Expected decode speed: 3.6 tok/s.
Yi 34B Chat (34B parameters) requires approximately 25.3 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 87.3 GB.
The recommended quantization is Q4_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 87.3 GB.
On NVIDIA DGX Spark 128GB, Yi 34B Chat achieves approximately 3.6 tokens per second decode speed with a time-to-first-token of 54198ms using F16 quantization.
For coding workloads, Yi 34B Chat on NVIDIA DGX Spark 128GB receives a F grade with 2.0 tok/s and 4K context.
On NVIDIA DGX Spark 128GB, Yi 34B Chat can safely use up to 110K tokens of context at F16 quantization. The model's official context limit is 200K, 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.
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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/yi-34b-chat-on-dgx-spark-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: