Can Qwen3.5 122B A10B run on NVIDIA DGX Spark 128GB?

YES — With Q6_K

D27Poor

Estimated from fit model

Qwen3.5 122B A10B needs ~128.6 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With Q6_K quantization, expect ~2 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: LowStack: BasicBottleneck: Host offload

Operating mode

Choose the run profile you care about

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.

Qwen3.5 122B A10B at Q3_K_M needs 75.3 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at Q6_K (128.6 GB) with high quality. 6 quantization levels fit.

Capabilities:

Select quantization to explore

F16 (Maximum quality) — 278.7 GB, exceeds 108.8 GB available

278.7 GB required108.8 GB available

256% VRAM needed

169.9 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.0 tok/s

TTFT

96800 ms

Safe context

Memory

278.7 GB / 108.8 GB

Offload

60%

Memory breakdown

Weights250.1 GB

KV Cache14.3 GB

Runtime1.2 GB

Headroom13.1 GB

See how fast it feels

With memory offload — actual speed may be lower

See how fast it feelsQwen3.5 122B A10B on NVIDIA DGX Spark 128GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
  - Full privacy: your prompts never leave your machine
  - No per-token cost or rate limits
  - Works offline once the model is downloaded
  - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

  Model size     Q4 (4-bit)    Q8 (8-bit)    FP16
  7B params      ~4.3 GB       ~7.5 GB       ~14 GB
  13B params     ~7.9 GB       ~13.9 GB      ~26 GB
  70B params     ~42.7 GB      ~74.9 GB      ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 2.0 tok/s decode · 96.8s TTFT (warm) · 5 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 20% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

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.

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.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 15.4 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

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

Quantization options

How Qwen3.5 122B A10B (122B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	47.6 GB	Low	C48
Q3_K_S	3	59.8 GB	Low	C48
NVFP4	4	68.3 GB	Medium	C48
Q4_K_MBest for your GPU	4	74.4 GB	Medium	C48
Q5_K_M	5	87.8 GB	High	F0
Q6_K	6	100.0 GB	High	F0
Q8_0	8	130.5 GB	Very High	F0
F16	16	250.1 GB	Maximum	F0

Get started

Copy-paste commands to run Qwen3.5 122B A10B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
  --hf-repo "unsloth/Qwen3.5-122B-A10B-GGUF" \
  --hf-file "Qwen3.5-122B-A10B-GGUF-Q3_K_M.gguf" \
  -c 4096 -ngl 99

Upgrade-Optionen

Hardware, die Qwen3.5 122B A10B gut ausführt

NVIDIA H200 141GBGünstige Wahl

141 GB VRAM (+13)4800 GB/s (+4527)

Raises estimated decode speed by about 2408%.62.7 tok/s Dekodierung

Raises estimated decode speed by about 2408%.

Adds memory headroom for longer context windows and future model growth.

ca. $30,000 MSRP

NVIDIA H200 PCIe 141GBBestes Preis-Leistungs-Verhältnis

141 GB VRAM (+13)4800 GB/s (+4527)

Raises estimated decode speed by about 2408%.62.7 tok/s Dekodierung

Raises estimated decode speed by about 2408%.

Adds memory headroom for longer context windows and future model growth.

ca. $30,000 MSRP

NVIDIA B200 180GBNVIDIA-Upgrade

180 GB VRAM (+52)8000 GB/s (+7727)

Raises estimated decode speed by about 4080%.104.5 tok/s Dekodierung

Raises estimated decode speed by about 4080%.

Adds memory headroom for longer context windows and future model growth.

ca. $30,000 MSRP

Frequently asked questions

Can NVIDIA DGX Spark 128GB run Qwen3.5 122B A10B?

Yes, NVIDIA DGX Spark 128GB can run Qwen3.5 122B A10B at Q6_K quantization (Very compromised (needs ~15.4 GB host RAM)). The recommended Q3_K_M requires 75.3 GB which exceeds available memory, but at Q6_K it needs only 128.6 GB. Expected decode speed: 2.0 tok/s.

How much VRAM does Qwen3.5 122B A10B need?

Qwen3.5 122B A10B (122B parameters) requires approximately 75.3 GB at Q3_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at Q6_K using 128.6 GB.

What is the best quantization for Qwen3.5 122B A10B?

The recommended quantization is Q3_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is Q6_K, which uses 128.6 GB.

What speed will Qwen3.5 122B A10B run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Qwen3.5 122B A10B achieves approximately 2.0 tokens per second decode speed with a time-to-first-token of 96800ms using Q6_K quantization.

Can NVIDIA DGX Spark 128GB run Qwen3.5 122B A10B for coding?

For coding workloads, Qwen3.5 122B A10B on NVIDIA DGX Spark 128GB receives a F grade with 2.0 tok/s and 4K context.

What context window can Qwen3.5 122B A10B use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Qwen3.5 122B A10B can safely use up to 4K tokens of context at Q6_K quantization. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if Qwen3.5 122B A10B feels slow on NVIDIA DGX Spark 128GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for Qwen3.5 122B A10B?

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.

See all results for NVIDIA DGX Spark 128GB See all hardware for Qwen3.5 122B A10B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/hf-unsloth--qwen3-5-122b-a10b-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: