willitrun·ai

Can EXAONE 3.5 7.8B Instruct run on NVIDIA DGX Spark 128GB?

YES — With F16

C42Usable
Estimated from fit model

EXAONE 3.5 7.8B Instruct needs ~31.2 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~14 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.

EXAONE 3.5 7.8B Instruct at Q4_K_M needs 6.9 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at F16 (31.2 GB) with maximum quality. 8 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 19.9 GB, 34.4 tok/s, Runs well
19.9 GB required108.8 GB available
18% VRAM used

Fit status

Runs well

Decode

34.4 tok/s

TTFT

5624 ms

Safe context

1.6M

Memory

19.9 GB / 108.8 GB

Memory breakdown

Weights4.8 GB
KV Cache0.9 GB
Runtime1.2 GB
Headroom13.1 GB

See how fast it feels

See how fast it feelsEXAONE 3.5 7.8B Instruct 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: 34.4 tok/s decode · 5.6s TTFT (warm) · 86 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 heavy6.2 tok/s17041 ms4K
CodingFToo heavy6.2 tok/s31242 ms4K
Agentic CodingFToo heavy6.2 tok/s45443 ms4K
ReasoningFToo heavy6.2 tok/s36923 ms4K
RAGFToo heavy6.2 tok/s56804 ms4K

Inference speed

EXAONE 3.5 7.8B Instruct inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for EXAONE 3.5 7.8B Instruct at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~109 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 / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M109.2Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M109.2Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M109.2Fits
NVIDIARTX 3090 24GB
24 GBQ4_K_M109.2Fits
RX 7900 XTX 24GB
24 GBQ4_K_M109.2Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M109.2Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M97.5Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M92.5Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M79.4Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M78.8Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M78.8Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M50.4Fits
NVIDIARTX 3060 12GB
12 GBQ4_K_M49.9Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M46.2Fits
NVIDIARTX 4060 8GB
8 GBQ4_K_M41.7Offloads
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M40.6Fits

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 EXAONE 3.5 7.8B Instruct (7.800000190734863B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.0 GB
LowD39
Q3_K_S
3
3.8 GB
LowD39
NVFP4
4
4.4 GB
MediumD39
Q4_K_M
4
4.8 GB
MediumD39
Q5_K_M
5
5.6 GB
HighD39
Q6_K
6
6.4 GB
HighD39
Q8_0
8
8.3 GB
Very HighD39
F16Best for your GPU
16
16.0 GB
MaximumC40

Get started

Copy-paste commands to run EXAONE 3.5 7.8B Instruct on your machine.

Run

lms load hf-lmstudio-community--exaone-3-5-7-8b-instruct-gguf && lms server start

Opciones de mejora

Hardware que ejecuta bien EXAONE 3.5 7.8B Instruct

Frequently asked questions

Can NVIDIA DGX Spark 128GB run EXAONE 3.5 7.8B Instruct?

Yes, NVIDIA DGX Spark 128GB can run EXAONE 3.5 7.8B Instruct at F16 quantization (Runs well). The recommended Q4_K_M requires 6.9 GB which exceeds available memory, but at F16 it needs only 31.2 GB. Expected decode speed: 14.3 tok/s.

How much VRAM does EXAONE 3.5 7.8B Instruct need?

EXAONE 3.5 7.8B Instruct (7.800000190734863B parameters) requires approximately 6.9 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 31.2 GB.

What is the best quantization for EXAONE 3.5 7.8B Instruct?

The recommended quantization is Q4_K_M, but on NVIDIA DGX Spark 128GB the best fitting quantization is F16, which uses 31.2 GB.

What speed will EXAONE 3.5 7.8B Instruct run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, EXAONE 3.5 7.8B Instruct achieves approximately 14.3 tokens per second decode speed with a time-to-first-token of 13499ms using F16 quantization.

Can NVIDIA DGX Spark 128GB run EXAONE 3.5 7.8B Instruct for coding?

For coding workloads, EXAONE 3.5 7.8B Instruct on NVIDIA DGX Spark 128GB receives a F grade with 6.2 tok/s and 4K context.

What context window can EXAONE 3.5 7.8B Instruct use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, EXAONE 3.5 7.8B Instruct can safely use up to 1.4M tokens of context at F16 quantization. The model's official context limit is —, but available memory constrains the safe maximum.

Is unified memory on NVIDIA DGX Spark 128GB as fast as VRAM for EXAONE 3.5 7.8B Instruct?

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 128GBSee all hardware for EXAONE 3.5 7.8B Instruct
Embed this result

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

<iframe src="https://willitrunai.com/embed/hf-lmstudio-community--exaone-3-5-7-8b-instruct-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: