DeepSeek-V4.1-Flash on DGX Spark (GB10): 128 GB unified, Does not fit, Rough estimate

DeepSeek-V4.1-Flash VRAM lists each catalog quant at 8,192 tokens.

GB10 is the superchip named on this record, NVIDIA DGX Spark (GB10, 128 GB unified). 128 GB LPDDR5x unified memory on the GB10 Superchip.

Does not fit. DeepSeek-V4.1-Flash FP8 safetensors on one DGX Spark (GB10) (128 GB LPDDR5x coherent unified system memory) estimates 476.18 GiB–549.77 GiB at 4,096 tokens, 1 sequence, FP16 KV, vllm, against 112.00 GiB net unified memory. The weight file is 510,286,023,000 bytes. Rough estimate. V4.1-Flash official packed weights on Spark. Coverage is partial: MLA KV is a latent bound, vision/Engram/MTP bytes are not separable, so this is a weights-lower-bound plus incomplete cache — not a full fit claim.

DeepSeek V4.1 Flash on DGX Spark (128 GB unified): Does not fit. DeepSeek-V4.1-Flash on DGX Spark (GB10). Estimate 476.18 GiB–549.77 GiB against 112.00 GiB net (FP8 safetensors, 4,096 tokens).

Conditional memory judgement for one configuration. Change context, quant, or engine and the conclusion can change. Configuration used on this page: FP8 safetensors, 4,096 cached tokens, 1 sequence, engine vllm. Status: Insufficient memory. Software: Not verified..

The generic calculator judges the canonical checkpoint. 3 community-tested deployment recipes are also listed for this setup.

Insufficient memoryNot verifiedThis result is an estimate, not a measured trace.3 known setups

Assumptions that affect this result

Model and recipes

Known working setups

3 known setups

Community and maintainer-tested deployment recipes for this model on this hardware platform.

DeepSeek-V4.1-Flash
2× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:EXL3 2.9 bpw (mul1)(2.9 bpw)
Runtime:vLLM· TP2
Offload:Engram n-gram tables (shards 47+48) → NVME
Tested:
  • ✓ generation
  • ✓ 262,144 context
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:31.6 tok/s· 1 stream

2-node DGX Spark setup serving DeepSeek-V4.1-Flash with vLLM tensor-parallel size 2 over ConnectX-7 RoCE, EXL3 2.9 bpw mul1 weights, and native NVMe-resident Engram tables.

DeepSeek-V4.1-Flash
3× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:Native MXFP4 MoE + FP8 Dense
Runtime:SGLang· TP3
Offload:Engram n-gram tables (189 GiB) → NVME
Tested:
  • ✓ generation
  • ✓ ~208K Tested (256K cfg)
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:37.9 tok/s· 1 stream

3-node DGX Spark cluster running native MXFP4 experts and FP8 dense weights with SGLang TP=3 over ConnectX-7 RoCE triangle, with NVMe-resident Engram tables.

DeepSeek-V4.1-Flash
4× NVIDIA DGX Spark (GB10, 128 GB unified)
Measured by upstream maintainer
Quant:Native MXFP4 MoE + FP8 Dense (TP=4)
Runtime:SGLang· TP4
Offload:Engram n-gram tables (189 GiB) → NVME
Tested:
  • ✓ generation
  • ✓ 1,048,576 context
  • ✓ tool calling
  • ✓ vision
  • ✓ speculative decoding
Measured:45.4 tok/s· 1 stream

4-node DGX Spark cluster running native MXFP4 MoE and FP8 dense weights with SGLang TP=4, verified 1M context needle test, and 8M pinned KV token pool.

Fixed page configuration

V4.1-Flash official packed weights on Spark. Coverage is partial: MLA KV is a latent bound, vision/Engram/MTP bytes are not separable, so this is a weights-lower-bound plus incomplete cache — not a full fit claim.

Technical identifiers and share data
  • Modeldeepseek-v4.1-flash
  • Hardwarenvidia-dgx-spark-128gb-unified
  • Quantizationfp8
  • Share fragment for this identityv2.eyJzY2hlbWFWZXJzaW9uIjoyLCJjYWxjdWxhdG9yVmVyc2lvbiI6IjAuMy4wIiwiZGF0YXNldFZlcnNpb24iOiIyMDI2LTEwLTAyLjEiLCJjb25maWciOnsibW9kZWxJZCI6ImRlZXBzZWVrLXY0LjEtZmxhc2giLCJoYXJkd2FyZUlkIjoibnZpZGlhLWRneC1zcGFyay0xMjhnYi11bmlmaWVkIiwiZGV2aWNlQ291bnQiOjEsInF1YW50aXphdGlvbklkIjoiZnA4IiwiY29udGV4dFRva2VucyI6NDA5NiwiY29uY3VycmVudFNlcXVlbmNlcyI6MSwiZW5naW5lIjoidmxsbSIsImt2VHlwZSI6ImZwMTYifX0

Memory breakdown

Weight artifact
475.24 GiB (510,286,023,000 bytes)
Raw KV cache
0.31 GiB (335,544,320 bytes)
Engine extras / workspace
0.63 GiB–74.22 GiB
Total estimated demand
476.18 GiB–549.77 GiB
Net calculator budget
112.00 GiB
OS / display reserve
16.00 GiB
Remaining vs net budget
-437.77 GiB–-364.18 GiB

549.77 GiB high estimate vs 112.00 GiB net

Enough memory does not mean this engine, quant, and OS will run. Support does not mean it will be fast.

Other published files on this device

Same model, device and context (4,096 tokens, 1 sequence, FP16 KV). Each row is one published weight-file set with its usual engine, sorted by memory.

QuantizationEngineEstimated memoryFit
FP8 safetensors This pagevllm476.18 GiB–549.77 GiBDoes not fit · Rough estimate
Open this combo in the calculatorKV Cache

Related pages

Sources

Calculator

This combo page keeps the route model and device. Customize to change them on the main calculator; the share then keeps that identity.

Loading catalog snapshot…

Choose a model first, then check a device.

Quantization

Device type

Workload

Context length primarily affects KV cache memory.

Advanced settings
Runtime

Engine and KV cache type for this estimate.

Workload

Overhead scenario and the prefill workspace.

Topology

How the model is split across devices. Memory is not added together.

Replica count is an advanced deployment option. Quantity is nodes or GPUs, not replicas.

Budget

System reserve and safety margin. An empty number keeps the previous value.

GiB (2^30 bytes)

%

Custom model

Import a config or type the architecture. Nothing is scanned until you import.

Parsed in the browser. The file is not uploaded.

Only huggingface.co, config.json, no token. Private repos are rejected.

Search or pick a catalog checkpoint to see memory demand.

Search or pick a catalog checkpoint to see memory demand.