Can Qwen 2.5 VL 72B run on NVIDIA DGX Spark 128GB?

YES — Runs Great

S85Excellent

Estimated from fit model

Qwen 2.5 VL 72B needs ~62.8 GB VRAM. NVIDIA DGX Spark 128GB has 108.8 GB. With Q4_K_M quantization, expect ~4 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: StandardBottleneck: Memory bandwidth

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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 62.8 GB, 4.1 tok/s, Runs well

62.8 GB required108.8 GB available

58% VRAM used

Fit status

Runs well

Decode

4.1 tok/s

TTFT

47734 ms

Safe context

33K

Memory

62.8 GB / 108.8 GB

Memory breakdown

Weights43.9 GB

KV Cache4.9 GB

Runtime0.9 GB

Headroom13.1 GB

See how fast it feels

See how fast it feelsQwen 2.5 VL 72B on NVIDIA DGX Spark 128GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step.

Given information:
  - Speed = 60 mph (miles per hour)
  - Time  = 2.5 hours

Formula: Distance = Speed x Time

Calculation:
  Distance = 60 mph x 2.5 h
           = 150 miles

The train travels 150 miles.

Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time.

Breakdown:
  - First half: 1.25 hours at 60 mph = 75 miles
  - Stop: 20 minutes (no distance)
  - Second half: 1.25 hours at 60 mph = 75 miles

Total distance: 150 miles (same)
Total time: 2.5 h + 0.33 h = 2.83 hours
Average speed: 150 / 2.83 = 53 mph

The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 4.1 tok/s decode · 47.7s TTFT (warm) · 10 tok/s prefill

What limits this setup

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.

Best improvement path

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.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs well	4.1 tok/s	26037 ms	33K
Coding	S	Runs well	4.1 tok/s	47734 ms	33K
Agentic Coding	S	Runs well	4.1 tok/s	69431 ms	33K
Reasoning	S	Runs well	4.1 tok/s	56412 ms	33K
RAG	S	Runs well	4.1 tok/s	86788 ms	33K

Inference speed

Qwen 2.5 VL 72B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Qwen 2.5 VL 72B at Q4_K_M across popular GPUs and Apple Silicon, including multi-GPU rigs, using the fastest local runtime per device. Fastest is 2× RX 7900 XTX 24GB at ~17 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / Mac	Memory	Quant	Speed (tok/s)	Fits?
2× RX 7900 XTX 24GB	48 GB	Q4_K_M	16.7	Heavy offload
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	14.9	Fits
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	13.8	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	11.5	Fits
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	11.0	Too big
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	10.9	Fits
2× RTX 4090 24GB	48 GB	Q4_K_M	8.8	Heavy offload
2× RTX 3090 24GB	48 GB	Q4_K_M	8.1	Heavy offload
4× RTX 3060 12GB	48 GB	Q4_K_M	7.1	Heavy offload
RTX 5090 32GB	32 GB	Q4_K_M	5.3	Too big
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	5.1	Too big
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	4.4	Too big
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	4.0	Too big
RX 7900 XTX 24GB	24 GB	Q4_K_M	2.6	Too big
RTX 4090 24GB	24 GB	Q4_K_M	2.0	Too big
RTX 4080 Super 16GB	16 GB	Q4_K_M	2.0	Too big
RTX 3090 24GB	24 GB	Q4_K_M	2.0	Too big
RTX 4070 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 3060 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 4060 8GB	8 GB	Q4_K_M	2.0	Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How Qwen 2.5 VL 72B (72B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	28.1 GB	Low	A83
Q3_K_S	3	35.3 GB	Low	A85
NVFP4	4	40.3 GB	Medium	S86
Q4_K_M	4	43.9 GB	Medium	S87
Q5_K_M	5	51.8 GB	High	S88
Q6_K	6	59.0 GB	High	S88
Q8_0Best for your GPU	8	77.0 GB	Very High	S88
F16	16	147.6 GB	Maximum	F0

Get started

Copy-paste commands to run Qwen 2.5 VL 72B on your machine.

Run

lms load Qwen2.5-VL-72B-Instruct && lms server start

Your hardware

More models your NVIDIA DGX Spark 128GB can run

Model	Params	Grade	Decode
Devstral 2 123B Instruct	123B	S	2.4 tok/s
Qwen 3.5 122B A10B	122B	S	6.6 tok/s
Mistral Small 4 119B	119B	S	7.1 tok/s
GPT-OSS 120B	117B	A	2.5 tok/s
Command A 111B	111B	S	2.6 tok/s

Frequently asked questions

Can NVIDIA DGX Spark 128GB run Qwen 2.5 VL 72B?

Yes, NVIDIA DGX Spark 128GB can run Qwen 2.5 VL 72B with a S grade (Runs well). Expected decode speed: 4.1 tok/s.

How much VRAM does Qwen 2.5 VL 72B need?

Qwen 2.5 VL 72B (72B parameters) requires approximately 62.8 GB of memory with Q4_K_M quantization.

What is the best quantization for Qwen 2.5 VL 72B?

The recommended quantization for Qwen 2.5 VL 72B is Q4_K_M, which balances quality and memory efficiency.

What speed will Qwen 2.5 VL 72B run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Qwen 2.5 VL 72B achieves approximately 4.1 tokens per second decode speed with a time-to-first-token of 47734ms using Q4_K_M quantization.

Can NVIDIA DGX Spark 128GB run Qwen 2.5 VL 72B for coding?

For coding workloads, Qwen 2.5 VL 72B on NVIDIA DGX Spark 128GB receives a S grade with 4.1 tok/s and 33K context.

What context window can Qwen 2.5 VL 72B use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Qwen 2.5 VL 72B can safely use up to 33K tokens of context. The model's official context limit is 33K, but available memory constrains the safe maximum.

What should I upgrade first if Qwen 2.5 VL 72B feels slow on NVIDIA DGX Spark 128GB?

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.

Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for Qwen 2.5 VL 72B?

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 Qwen 2.5 VL 72B

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/qwen-2.5-vl-72b-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: