llamaperf

llama.cpp on the NVIDIA DGX Spark

On the NVIDIA DGX Spark, llama.cpp runs Nemotron 3 120B · 12B active at 4-bit at a median 17.2 tokens per second for generation, from 2 plain runs (context not stated).

Speed by model on the NVIDIA DGX Spark

Plain runs only: one device, one request, no speculative decoding, the whole model in memory. Each row is one model size at one bit class, with the other engines' plain runs of the same model on this card beside it. Context length and build still differ between runs, and each side shows its own.

Modelllama.cppOther engines
Nemotron 3 120B · 12B active 4-bit17.2 t/smedian of 2, context not statedno other engine reported
Gemma 4 26B · 4B active 4-bit69.9 t/sone report, 256K context
vLLM 48.2 t/sone report, context not stated
Ling-3.0 124B · 5.1B active 5-bit35.7 t/sone report, 256K contextno other engine reported
Ornith1.5 35B · 3B active 6-bit69.0 t/sone report, 128K contextno other engine reported
Qwen3.8 125B · 6B active 4-bit24.5 t/sone report, 128K context
SGLang 35.0 t/sone report, 256K context

11 llama.cpp reports on the NVIDIA DGX Spark

Newest first. A run on several cards, with speculative decoding, with part of the model in system RAM or with batched requests says so, since each describes a different setup.

Filter these reports on the homepage

Frequently asked

How fast is llama.cpp on the NVIDIA DGX Spark?

On the NVIDIA DGX Spark, llama.cpp runs Nemotron 3 120B · 12B active at 4-bit at a median 17.2 tokens per second for generation, from 2 plain runs (context not stated).

Is llama.cpp faster than other engines on the NVIDIA DGX Spark?

Same card, same model size and bit class, plain runs only: Gemma 4 26B · 4B active at 4-bit gives llama.cpp 69.9 t/s (1 run) and vLLM 48.2 t/s (1). Context length and engine build differ between the runs, so treat it as a lead, not a benchmark.