Can the RTX Spark N1X (128 GB) run Qwen3.6 35B A3B?

Yes. Qwen3.6 35B A3B fits the RTX Spark N1X (128 GB)'s 128 GB at Q4_K_M (about 22.8 GB needed), running at an estimated 60 tok/s. There's room for up to FP16 if you want higher quality.

Memory
128 GB
Needs at Q4
22.8 GB
Headroom
105.2 GB
Speed (Q4_K_M)
~60 tok/s

Every quantization

Qwen3.6 35B A3B (36B, 3B active) on 128 GB

QuantWeightsNeedsFitEst. speed
Q4_K_M21 GB22.8 GBFits easily~60 tok/s
Q5_K_M26 GB27.8 GBFits easily~48 tok/s
Q8_039 GB40.8 GBFits easily~32 tok/s
FP1672 GB73.8 GBFits easily~17 tok/s

Estimates. Needs = weights + 1.8 GB for KV cache and runtime at modest context. Speed is single-stream decode scaled from the RTX Spark N1X (128 GB)'s 273 GB/s bandwidth (Estimated from memory bandwidth (llama.cpp decode); bandwidth assumed equal to DGX Spark (GB10), which shares the 6,144-core GPU - NVIDIA has not published an N1X figure). Long contexts need more memory and run slower.

Run it

Copy, paste, go

llama-server -hf unsloth/Qwen3.6-35B-A3B-GGUF -ngl 99

Ollama pulls a Q4 build by default. Pick a larger quant only if the table above says it fits. Full Qwen3.6 35B A3B details →

Compare

Same model, other hardware - and other models on this card

Qwen3.6 35B A3B on other hardware

Also runs on the RTX Spark N1X (128 GB)

Frequently asked

Quick answers

Can the NVIDIA RTX Spark N1X (128 GB) run Qwen3.6 35B A3B?

Yes. Qwen3.6 35B A3B fits the RTX Spark N1X (128 GB)'s 128 GB at Q4_K_M (about 22.8 GB needed), running at an estimated 60 tok/s. There's room for up to FP16 if you want higher quality.

How much VRAM does Qwen3.6 35B A3B need?

About 21 GB of weights at Q4_K_M, 39 GB at Q8_0 and 72 GB at FP16. Add roughly 1.8 GB for the KV cache and runtime at modest context lengths.

How fast is Qwen3.6 35B A3B on the RTX Spark N1X (128 GB)?

Roughly 60 tokens per second at Q4_K_M (single user, llama.cpp-style decode). This is an estimate from the RTX Spark N1X (128 GB)'s 273 GB/s memory bandwidth; as a mixture-of-experts model only about 3B parameters are read per token, which is why it is faster than its size suggests.