Benched a 124B on one DGX Spark for a week and published all of it — 38.7 tok/s on the fastest path he found, 2.4x DeepSeek V4 Flash on the same box

Reddit r/LocalLLaMA News

Summary

An independent benchmark by sudoingX shows the Ling-3.0-flash model runs at 38.7 tok/s on a single DGX Spark with official INT4 quantization, 2.4x faster than DeepSeek V4 Flash on the same hardware, after a correction clarifying the quants do work.

sudoingX on X spent a week on this and posted his wrap-up. The hardware is his. He isn't affiliated with us and we didn't see any of it before he put it out — I work on Ling at inclusionAI. Where he landed on one Spark: 38.7 tok/s on the official INT4 once it's configured right, 35.2 on the community GGUF, 2.4x what DeepSeek V4 Flash does on the same machine. His phrasing is that Ling-3.0-flash earned a permanent seat on his box. What got my attention was the correction in the middle. He'd posted that our official quants don't run on a single Spark. Two days later he posted that they do, that they're the fastest path he has now, and quote-tweeted his own earlier post to say so. Most of those numbers have the method sitting next to them on his timeline, so you don't have to take it from me. One Spark and one person, over a week. He's been at this longer than I've been reading about it.
Original Article

Similar Articles

Deepseek V4 flash performance on DGX Spark

Reddit r/LocalLLaMA

A Reddit user shares their experience running DeepSeek V4 Flash on a dual-ASUS GX10 DGX Spark setup, detailing performance metrics, configuration, and power consumption, with throughput benchmarks across various context lengths.

Lawyer with too many GPUs, part 3: DeepSeek-V4.1-Flash on 2x DGX Spark + an old 3090 box. 2,600+ tok/s prefill to 256K, 322 tok/s structured output, full stack and raw data published

Reddit r/LocalLLaMA

A lawyer and PLI Labs founder publishes full benchmark data for running DeepSeek-V4.1-Flash-1017 (2.75 bpw EXL3) across two DGX Sparks with a 3090 box handling RDMA-served tables and a speculative drafter, hitting 2,600+ tok/s prefill to 256K context and 322 tok/s structured output. All code, launch scripts, and raw JSON are released publicly, with the author openly noting where his build loses to competing 2x Spark setups.