Can Magistral Small 2507 run on NVIDIA DGX Spark 128GB?

YES — Runs Great

A83Great

Estimated from fit model

Magistral Small 2507 needs ~31.3 GB VRAM. NVIDIA DGX Spark 128GB has 108.8 GB. With Q4_K_M quantization, expect ~12 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: LowStack: BasicBottleneck: Balanced

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) — 31.3 GB, 12.0 tok/s, Runs well

31.3 GB required108.8 GB available

29% VRAM used

Fit status

Runs well

Decode

12.0 tok/s

TTFT

16096 ms

Safe context

131K

Memory

31.3 GB / 108.8 GB

Memory breakdown

Weights14.6 GB

KV Cache2.4 GB

Runtime1.2 GB

Headroom13.1 GB

See how fast it feels

See how fast it feelsMagistral Small 2507 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: 12.0 tok/s decode · 16.1s TTFT (warm) · 30 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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs well	12.0 tok/s	8780 ms	131K
Coding	A	Runs well	12.0 tok/s	16096 ms	131K
Agentic Coding	A	Runs well	12.0 tok/s	23413 ms	131K
Reasoning	A	Runs well	12.0 tok/s	19023 ms	131K
RAG	A	Runs well	12.0 tok/s	29266 ms	131K

Quantization options

How Magistral Small 2507 (24B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	9.4 GB	Low	A81
Q3_K_S	3	11.8 GB	Low	A81
NVFP4	4	13.4 GB	Medium	A81
Q4_K_M	4	14.6 GB	Medium	A82
Q5_K_M	5	17.3 GB	High	A82
Q6_K	6	19.7 GB	High	A82
Q8_0	8	25.7 GB	Very High	A83
F16Best for your GPU	16	49.2 GB	Maximum	S88

Get started

Copy-paste commands to run Magistral Small 2507 on your machine.

Run

ollama run magistral

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
Qwen3-Coder 30B A3B Instruct	30.5B	S	24.8 tok/s
Qwen 3.5 27B	27B	A	10.7 tok/s
Qwen 3.6 27B	27B	A	10.8 tok/s
Qwen 3.5 122B A10B	122B	S	6.6 tok/s

Frequently asked questions

Can NVIDIA DGX Spark 128GB run Magistral Small 2507?

Yes, NVIDIA DGX Spark 128GB can run Magistral Small 2507 with a A grade (Runs well). Expected decode speed: 12.0 tok/s.

How much VRAM does Magistral Small 2507 need?

Magistral Small 2507 (24B parameters) requires approximately 31.3 GB of memory with Q4_K_M quantization.

What is the best quantization for Magistral Small 2507?

The recommended quantization for Magistral Small 2507 is Q4_K_M, which balances quality and memory efficiency.

What speed will Magistral Small 2507 run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Magistral Small 2507 achieves approximately 12.0 tokens per second decode speed with a time-to-first-token of 16096ms using Q4_K_M quantization.

Can NVIDIA DGX Spark 128GB run Magistral Small 2507 for coding?

For coding workloads, Magistral Small 2507 on NVIDIA DGX Spark 128GB receives a A grade with 12.0 tok/s and 131K context.

What context window can Magistral Small 2507 use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, Magistral Small 2507 can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for Magistral Small 2507?

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 Magistral Small 2507

Embed this result▼

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

<iframe src="https://willitrunai.com/embed/magistral-small-2507-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: