Can internlm2 5 20b chat run on NVIDIA DGX Spark 128GB?

YES — With F16

C44Usable
Estimated from fit model

internlm2 5 20b chat needs ~57.6 GB VRAM. NVIDIA DGX Spark 128GB has 0 MB. With F16 quantization, expect ~6 tok/s.

Runtime: OllamaCapacity: RoomyBandwidth: LowStack: BasicBottleneck: 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.

internlm2 5 20b chat at Q4_K_M needs 15.7 GB — too much for NVIDIA DGX Spark 128GB (0.0 GB). Runs at F16 (57.6 GB) with maximum quality. 8 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 28.8 GB, 13.4 tok/s, Runs well
28.8 GB required108.8 GB available
26% VRAM used

Fit status

Runs well

Decode

13.4 tok/s

TTFT

14420 ms

Safe context

562K

Memory

28.8 GB / 108.8 GB

Memory breakdown

Weights12.2 GB
KV Cache2.3 GB
Runtime1.2 GB
Headroom13.1 GB

See how fast it feels

See how fast it feelsinternlm2 5 20b chat 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: 13.4 tok/s decode · 14.4s TTFT (warm) · 34 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
ChatCRuns well13.4 tok/s7865 ms562K
CodingFToo heavy2.4 tok/s80109 ms4K
Agentic CodingCRuns well13.4 tok/s20974 ms562K
ReasoningCRuns well13.4 tok/s17041 ms562K
RAGCRuns well13.4 tok/s26217 ms562K

Inference speed

internlm2 5 20b chat inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for internlm2 5 20b chat at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~98 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_M98.4Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M62.8Fits
RX 7900 XTX 24GB
24 GBQ4_K_M56.7Fits
NVIDIARTX 3090 24GB
24 GBQ4_K_M53.7Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M45.6Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M38.0Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M36.1Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M35.6Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M35.6Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M31.7Heavy offload
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M22.4Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M19.7Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M18.0Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M11.2Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M7.1Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.6Too 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 internlm2 5 20b chat (20B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
7.8 GB
LowD39
Q3_K_S
3
9.8 GB
LowD39
NVFP4
4
11.2 GB
MediumD39
Q4_K_M
4
12.2 GB
MediumD39
Q5_K_M
5
14.4 GB
HighD40
Q6_K
6
16.4 GB
HighD40
Q8_0
8
21.4 GB
Very HighC41
F16Best for your GPU
16
41.0 GB
MaximumC45

Get started

Copy-paste commands to run internlm2 5 20b chat on your machine.

Run

lms load hf-bartowski--internlm2-5-20b-chat-gguf && lms server start

Upgrade-Optionen

Hardware, die internlm2 5 20b chat gut ausführt

Frequently asked questions

Can NVIDIA DGX Spark 128GB run internlm2 5 20b chat?

Yes, NVIDIA DGX Spark 128GB can run internlm2 5 20b chat at F16 quantization (Runs well). The recommended Q4_K_M requires 15.7 GB which exceeds available memory, but at F16 it needs only 57.6 GB. Expected decode speed: 5.6 tok/s.

How much VRAM does internlm2 5 20b chat need?

internlm2 5 20b chat (20B parameters) requires approximately 15.7 GB at Q4_K_M quantization. On NVIDIA DGX Spark 128GB, it fits at F16 using 57.6 GB.

What is the best quantization for internlm2 5 20b chat?

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

What speed will internlm2 5 20b chat run at on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, internlm2 5 20b chat achieves approximately 5.6 tokens per second decode speed with a time-to-first-token of 34614ms using F16 quantization.

Can NVIDIA DGX Spark 128GB run internlm2 5 20b chat for coding?

For coding workloads, internlm2 5 20b chat on NVIDIA DGX Spark 128GB receives a F grade with 2.4 tok/s and 4K context.

What context window can internlm2 5 20b chat use on NVIDIA DGX Spark 128GB?

On NVIDIA DGX Spark 128GB, internlm2 5 20b chat can safely use up to 366K tokens of context at F16 quantization. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if internlm2 5 20b chat 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 internlm2 5 20b chat?

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 internlm2 5 20b chat
Embed this result

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

<iframe src="https://willitrunai.com/embed/hf-bartowski--internlm2-5-20b-chat-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: