First - credits where credits due to post by @tonyd615 and @11_p who pointed me to a right direction: DeepSeek-V4-Flash (official FP8) running across 2x DGX Spark — TP=2, MTP, 200K ctx, recipe + numbers - #174 by 11_p as more so to original creator of recipe @aidendle94 and reddit post Reddit - Plea…

[image] Validate your local LLM advertised KV cache against real pressure; see exactly how old contexts get evicted from cache DGX Spark / GB10 Hello, For the last few days I’ve been working on cache management on vLLM with my 2x DGX Spark and DeepSeek v4 Flas…

Thanks for the log, very strange that it’s so different. My setup is made by codex from the Reddit post, and I even had it go back and verify against your posted recipe and it found no significant differences apart from my 0.8 gpu-memory-utilization and my 400k max-model-len. The earlier log snippet…

It’s not about drivers. I would guess you either using FP16 cache, that would perfectly match x0.5 amount of tokens your logs show or you are using Ray instead of VLLM-distributed, Ray is absolutely proved to have a big RAM overhead, leaving much less space for cache. Experimented a lot and stopped …

Looks like it’s just a matter of vllm calculating things differently when you change the model-len, with 1M I get 2.55 x concurrency so similar to your numbers

Yes its true, it often gives BS numbers in terms of total cache in tokens available for the newer architectures, but the session size x concurrency was always correct in my observations.

Yea I always just used session size x concurrency numbers from the logs to determine max possible context as I expected that product to be fixed, I didn’t expect the total kv budget to change drastically from just increasing max-model-len.

If your DS4F checkpoint broker today - DeepSeek published a small update and HF mistakingly focus on the digest and cannot see weights anymore. Solution - point to a specific working hash deepseek-ai/DeepSeek-V4-Flash --revision 6976c7ff1b30a1b2cb7805021b8ba4684041f136

I’ve found out the cause with the help of Codex agent, it’s the Clash proxy’s TUN which capture all the network packages…

Where can I follow the release? Is it your vllm github repo or docker hub? Looking forward to the kv fix.

aidendle94/sparkrun-vllm-ds4-gb10 - Docker Image Updated 11 days ago. Please let us know when you push!

DeepSeek v4 Flash (Aiden Recipe from Reddit) - 1M token session operational, Cuda 12.1 tailored for DGX Spark GB10

Accelerated Computing DGX Spark / GB10 User Forum DGX Spark / GB10

aidendle94 June 11, 2026, 8:55pm 61

I have a small fix I will be pushing tonight to improve long running instance reliability on kv cache.

Topic		Replies	Views
DeepSeek-V4-Flash (official FP8) running across 2x DGX Spark — TP=2, MTP, 200K ctx, recipe + numbers DGX Spark / GB10 deepseek	261	32437	August 21, 2026
Deepseek v4 Flash on 2 Nodes DGX Spark / GB10 Projects deepseek	71	9373	June 15, 2026
Instructions for running Deepseek-v4-flash with DSpark using Eugr's repo DGX Spark / GB10 Projects deepseek	100	10375	September 22, 2026
DeepSeek-V4-Flash on 4× DGX Spark via vLLM (jasl fork, TP=4, RDMA, MTP) — 49–54 tok/s single-stream, full recipe + the traps DGX Spark / GB10 Projects deepseek	3	1841	June 19, 2026
DeepSeekV4-Flash hybrid quant, 1x DGX Spark: antirez's optimized 128 GB MLX recipe ported to vLLM for GB10 DGX Spark / GB10 Projects deepseek	18	2866	May 11, 2026
C1 1058pp/s, 52 tg/s on 1x dgx spark on Deepseek V4 flash 0731 full 256 experts DGX Spark / GB10 Projects deepseek	94	7409	September 5, 2026
Qwen 3.8 Flash Next on two SPARKs DGX Spark / GB10	56	3947	September 29, 2026
Deepseek V4 released DGX Spark / GB10 deepseek	143	20988	May 18, 2026
Official NVidia optimized DeepSeek-V4-Flash models? DGX Spark / GB10 deepseek	28	3835	July 11, 2026
DeepSeek-v4-Flash-0731-DSpark-1M-NVFP4-KV-2x-DGX-Spark DGX Spark / GB10 deepseek	20	12461	August 27, 2026

DeepSeek v4 Flash (Aiden Recipe from Reddit) - 1M token session operational, Cuda 12.1 tailored for DGX Spark GB10

Related topics