VOOZH about

URL: https://willitrunai.com/can-run/qwen-3-1.7b-on-dgx-spark-128gb


Can Qwen 3 1.7B run on NVIDIA DGX Spark 128GB?

YES — With F16

B61Good
Estimated from fit model

Qwen 3 1.7B needs ~19.4 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~24 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: LowStack: BasicBottleneck: Balanced
Share:

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.

Qwen 3 1.7B at Q4_K_M needs 3.9 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at F16 (19.4 GB) with maximum quality. 8 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 17.0 GB, 23.8 tok/s, Runs well
17.0 GB required108.8 GB available
16% VRAM used

Fit status

Runs well

Decode

23.8 tok/s

TTFT

8134 ms

Safe context

33K

Memory

17.0 GB / 108.8 GB

Memory breakdown

Weights1.0 GB
KV Cache1.7 GB
Runtime1.2 GB
Headroom13.1 GB

See how fast it feels

See how fast it feelsQwen 3 1.7B 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: 23.8 tok/s decode · 8.1s TTFT (warm) · 60 tok/s prefill

What limits this setup

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.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy23.8 tok/s4437 ms4K
CodingFToo heavy23.8 tok/s8134 ms4K
Agentic CodingFToo heavy23.8 tok/s11832 ms4K
ReasoningFToo heavy23.8 tok/s9613 ms4K
RAGFToo heavy23.8 tok/s14790 ms4K

Quantization options

How Qwen 3 1.7B (1.7000000476837158B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
0.7 GB
LowB59
Q3_K_S
3
0.8 GB
LowB59
NVFP4
4

Get started

Copy-paste commands to run Qwen 3 1.7B on your machine.

Run

ollama run qwen3:1.7b

Upgrade options

Hardware that runs Qwen 3 1.7B well

Mac Studio M3 Ultra 256GBBudget pick
256 GB Unified (+128)819 GB/s (+546)
B
Adds memory headroom for longer context windows and future model growth.23.8 tok/s decode

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

~$6,999 MSRP

Frequently asked questions

See all results for NVIDIA DGX Spark 128GBSee all hardware for Qwen 3 1.7B
1.0 GB
Medium
B59
Q4_K_M
4
1.0 GB
MediumB59
Q5_K_M
5
1.2 GB
HighB59
Q6_K
6
1.4 GB
HighB59
Q8_0
8
1.8 GB
Very HighB59
F16Best for your GPU
16
3.5 GB
MaximumB59

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.