VOOZH about

URL: https://willitrunai.com/can-run/devstral-2-123b-on-dgx-spark-128gb


Can Devstral 2 123B Instruct run on NVIDIA DGX Spark 128GB?

YES — Tight Fit

S86Excellent
Estimated from fit model

Devstral 2 123B Instruct needs ~94.4 GB VRAM. NVIDIA DGX Spark 128GB has 108.8 GB. With Q4_K_M quantization, expect ~2 tok/s.

Runtime: llama.cppCapacity: TightBandwidth: LowStack: StandardBottleneck: Memory bandwidth
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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 94.4 GB, 2.4 tok/s, Tight fit
94.4 GB required108.8 GB available
87% VRAM used

Fit status

Tight fit

Decode

2.4 tok/s

TTFT

81545 ms

Safe context

59K

Memory

94.4 GB / 108.8 GB

Memory breakdown

Weights75.0 GB
KV Cache5.4 GB
Runtime0.9 GB
Headroom13.1 GB

See how fast it feels

See how fast it feelsDevstral 2 123B Instruct on NVIDIA DGX Spark 128GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 2.4 tok/s decode · 81.5s TTFT (warm) · 6 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

WorkloadGradeFitDecodeTTFTContext
ChatSTight fit2.4 tok/s44479 ms59K
CodingSTight fit2.4 tok/s81545 ms59K
Agentic CodingSTight fit2.4 tok/s118611 ms59K
ReasoningFToo heavy2.0 tok/s114400 ms4K
RAGSTight fit2.4 tok/s148264 ms59K

Quantization options

How Devstral 2 123B Instruct (123B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
48.0 GB
LowS91
Q3_K_S
3
60.3 GB
LowS91
NVFP4Best for your GPU

Get started

Copy-paste commands to run Devstral 2 123B Instruct on your machine.

Run

lms load Devstral-2-123B-Instruct-2512 && lms server start

Frequently asked questions

See all results for NVIDIA DGX Spark 128GBSee all hardware for Devstral 2 123B Instruct
4
68.9 GB
Medium
S91
Q4_K_M
4
75.0 GB
MediumF0
Q5_K_M
5
88.6 GB
HighF0
Q6_K
6
100.9 GB
HighF0
Q8_0
8
131.6 GB
Very HighF0
F16
16
252.2 GB
MaximumF0

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.