DGX Spark Clusters by the Numbers: A Sizing Guide Across 1, 2, 3, and 4 Nodes

Written by

in

NVIDIA’s DGX Spark (GB10) started as a deskside curiosity — a 128GB unified-memory workstation drawing ~38W from the GPU during inference. Over the last several weeks, a wave of open-source recipes and community benchmarks has turned the Spark into a modular building block. Users are connecting 2, 3, and 4 units directly — no switch required — and publishing reproducible configurations for models ranging from 35B parameters past 1 trillion.

We collected the published benchmarks across all four cluster sizes to understand where each configuration makes sense.

Single GB10 (128GB unified)

The single-Spark sweet spot is dense models under 35B parameters and MoE models with small active footprints:

ModelTotalActiveQuantSpeedQualitySource
Qwen3.6-35B-A3B35B3B (A3B)NVFP4700+ tok/s agg (64 users)Excellentspark-bench
Qwen3.6-27B-NVFP427B27B (dense)NVFP484.7→183 tok/s (b16)Very highNVIDIA on HF
Nemotron Puzzle 75B-A9B75B9.3B (MoE+Mamba)NVFP4~38-42 solo / ~75 aggStrongGitHub recipe
Nemotron-3-Super-120B-A12B120B12B (MoE)NVFP4~20-30 tok/sFrontier-ishcommunity post
Hy3 (Tencent)295B~21B (MoE, 8/192)FP8/NVFP4~30 tok/s (128GB Mac)Beats DS V4Tencent
DeepSeek V4 Flash (GGUF)~671B~37B (MoE)8-bit GGUF~8-15 tok/sFrontierUnsloth
GLM-5.2 (Colibri, 25GB RAM)744B~40B (MoE)Colibri C (disk)~4-8 tok/sWorks on laptopindependent dev

We think the single Spark makes the most sense for organizations that need to serve multiple models side by side, or run inference and fine-tuning on separate nodes. At roughly $4K per unit, there is no other Blackwell-class compute at this power envelope.

Paired GB10s (256GB unified, approximately $8K total)

With two Sparks connected directly, the range of models expands meaningfully:

ModelTotalActiveQuantSpeedQualitySource
DeepSeek V4 Flash~671B~37B (MoE)NVFP455-60 tok/s, 1M ctxFrontiercommunity post
DeepSeek V4 Flash (NVFP4 KV)~671B~37B (MoE)NVFP4 KV cache~55-60 tok/s, 1.5M poolFrontierNVFP4 KV recipe
GLM-5.2 744B (pruned)744B~40B (MoE)NVFP4 + 15% prune~15→24 tok/s (DPC4+MTP4)Near-full acc, 256Kcommunity post
MiniMax M3.0428B~45B (MoE)NVFP436 tok/sHighvLLM PR

We think this is the best price-to-performance point in the local-inference market today. The 256GB configuration can run DeepSeek V4 Flash at 55-60 tok/s with a 1M-token context for $8,000 — roughly the cost of a single NVIDIA RTX PRO 6000 with less memory and no networking. The paired configuration hits a performance ceiling around 300B unquantized parameters; beyond that, quantization becomes necessary.

Three GB10s (384GB unified, approximately $12K)

The three-Spark cluster is the most thoroughly documented configuration in the community, largely because of the MiMo V2.5 Omni work:

ModelTotalActiveQuantSpeedQualitySource
MiMo V2.5 Omni310B15B (MoE)FP8/NVFP4~39 tok/s97.3 TrueScorefull recipe
MiMo V2.5 (concurrency)310B15B (MoE)FP8/NVFP437→82 tok/s (1→8 agents)94.4 TrueScorebenchmark
MiMo V2.5 (thinking ON/OFF)310B15B (MoE)FP8/NVFP497.3@1.2s / 88.9@2.4sDetailed evaleval results
GLM-5.2 744B (no pruning)744B~40B (MoE)NVFP4+FP3+MXFP8Full vLLM speedNear-full accvLLM config
GLM-5.2 REAP 469B469B~40B (MoE)NVFP4~4.4 tok/s, 256K ctxGoodREAP post
GLM-5.2 vs Kimi K2.7 (~1T)754B/~1T~40B/~40B (MoE)2-bit7.6 / 10.6 tok/s96.4 / 93.5comparison
MiniMax M3.0428B~45B (MoE)NVFP4~36 tok/sHighvLLM PR

The three-Spark setup requires no external switch — the units connect directly. The 384GB of unified memory is the threshold where full 744B models like GLM-5.2 fit without pruning. MiMo V2.5 Omni is the standout: 97.3 TrueScore at 1.2 seconds with thinking off, full multimodal (text, image, video, audio), and 82 tok/s aggregate across eight agents.

Four GB10s (512GB unified, approximately $16K) and Beyond

ModelTotalActiveQuantSpeedQualitySource
GLM-5.2 744B (NVFP4+15% prune)744B~40B (MoE)NVFP4+FP3+MXFP8~22 tok/s, MTPNear-full acccommunity post
GLM-5.2 744B (DPC4+MTP4)744B~40B (MoE)NVFP4~23-24 tok/s @ 128KNear-full accoptimization
GLM-5.2 744B (best config)744B~40B (MoE)NVFP4+FP3Higher than 22 tok/sFull, no prunebest config

A community workaround exists for connecting four Sparks without a switch. At the extreme end, one builder assembled six GX10s (the ASUS-branded Spark), two Ultra nodes, and two Minis into a 1.5TB unified-memory cluster for $17,000, repurposing retired Ethereum mining frames.

Where Each Configuration Fits

ConfigurationUnified MemoryCostLeading ModelPerformanceBest for
1x GB10128 GB~$4KQwen3.6-35B-A3B700+ tok/s (64 users)Multi-model serving, single-model inference
2x GB10256 GB~$8KDeepSeek V4 Flash55-60 tok/s, 1M ctxBest price-to-performance for frontier models
3x GB10384 GB~$12KMiMo V2.5 Omni39 tok/s, 97.3 TrueScoreFull multimodal, largest model selection
4x GB10512 GB~$16KGLM-5.2 (full)22-24 tok/sMaximum capacity per node, full-precision MoE

We think the most interesting inflection point is at two Sparks. The 256GB configuration can run DeepSeek V4 Flash at 55-60 tok/s with a 1M-token context for $8,000 — roughly the cost of a single NVIDIA RTX PRO 6000 with less memory and no cabling or networking. The three-Spark cluster, at 384GB, is the threshold where full 744B models fit without pruning. Above that, the incremental memory matters less than the community recipe ecosystem, which is currently densest at the two- and three-Spark levels.

More posts

© MarketIntelligenceResearch.com