Qwen3.5 35B A3B needs ~90.1 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~3 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
7.7 tok/s
TTFT
25234 ms
Safe context
286K
Memory
39.7 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 | F | Too heavy | 2.0 tok/s | 52800 ms | 4K |
| Coding | F | Too heavy | 2.0 tok/s | 96800 ms | 4K |
| Agentic Coding | F | Too heavy | 2.0 tok/s | 140800 ms | 4K |
| Reasoning | F | Too heavy | 2.0 tok/s | 114400 ms | 4K |
| RAG | F | Too heavy | 2.0 tok/s | 176000 ms | 4K |
How Qwen3.5 35B A3B (35B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.7 GB | Low | C40 |
Q3_K_S | 3 | 17.2 GB | Low | C41 |
NVFP4 | 4 | 19.6 GB | Medium | C41 |
Q4_K_M | 4 | 21.3 GB | Medium | C41 |
Q5_K_M | 5 | 25.2 GB | High | C42 |
Q6_K | 6 | 28.7 GB | High | C43 |
Q8_0 | 8 | 37.5 GB | Very High | C45 |
F16Best for your GPU | 16 | 71.8 GB | Maximum | C48 |
Copy-paste commands to run Qwen3.5 35B A3B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "lmstudio-community/Qwen3.5-35B-A3B-GGUF" \
--hf-file "Qwen3.5-35B-A3B-GGUF-Q4_K_M.gguf" \
-c 4096 -ngl 99Opciones de mejora
NVIDIA H200 141GBOpción económicaSube la velocidad estimada de decodificación alrededor de un 2353%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
NVIDIA H200 PCIe 141GBMejor relación calidad-precioSube la velocidad estimada de decodificación alrededor de un 2353%.
Añade margen de memoria para más contexto y para que el modelo envejezca mejor.
~$30,000 MSRP
NVIDIA B200 180GBMejora NVIDIASube la velocidad estimada de decodificación alrededor de un 3988%.
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 Qwen3.5 35B A3B at F16 quantization (Tight fit). The recommended Q4_K_M requires 26.7 GB which exceeds available memory, but at F16 it needs only 90.1 GB. Expected decode speed: 3.2 tok/s.
Qwen3.5 35B A3B (35B parameters) requires approximately 26.7 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 90.1 GB.
The recommended quantization is Q4_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 90.1 GB.
On NVIDIA DGX Spark 128GB, Qwen3.5 35B A3B achieves approximately 3.2 tokens per second decode speed with a time-to-first-token of 60574ms using F16 quantization.
For coding workloads, Qwen3.5 35B A3B on NVIDIA DGX Spark 128GB receives a F grade with 2.0 tok/s and 4K context.
On NVIDIA DGX Spark 128GB, Qwen3.5 35B A3B can safely use up to 89K tokens of context at F16 quantization. The model's official context limit is —, 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/hf-lmstudio-community--qwen3-5-35b-a3b-gguf-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: