What’s the best way to run DeepSeek-V4.1-Flash on 4 DGX Sparks?
As I see it, there isn’t one answer. It depends on what you need. One fast user/agent, or many at once? Huge documents? Long agentic sessions? Original weights, or compressed? We needed these answers to figure out the optimal stacks for our CVE pipelines. So we took six community recipes, ran each exactly as its author serves it on the same four Sparks, and measured them all the same way, to see what each one is best at.
Quality first: on our tests it’s level. All six pass 71 of 75 qeval tasks and find every passphrase hidden in a 1M-token prompt, compressed weights included. So the choice comes down to how you use it:
@bertholomusai (TensorFold, 4-bit EXL3): the fastest single user (77 tok/s), the quickest reply while someone else’s long prompt is being read (0.9 s), and 16 full 1M-token sessions at once.
@Tech2Wild (TensorFold, 3.5-bit EXL3): the fastest coding for one user (134 tok/s), and the most memory left free on each node.
J-M-Recipes, @JamesMeadlock (vLLM on @christopherowen’s fork, original weights): the most users at once (32 seats, 288 tok/s with 16 users), quick replies during long reads (1.1 s), and 11.5 full 1M sessions. In our long-session agent tests it started the next turn fastest.
@majewskizby (SGLang, original weights): the fastest at reading huge documents, 1M tokens in 3.4 minutes.
@MiaAI_lab (TensorFold, original weights): 16 full 1M sessions at once on the original weights.
@MiaAI_lab (SGLang, original weights): the production line @majewskizby’s profile builds on.
Medians of three runs, temperature 0, thinking off, on an NVIDIA SN3700 switch.
All credit to the authors: these are their recipes, we only ran and measured them. Kudos for publishing them openly, with every setting, patch and number needed to reproduce them, and for the speed you ship at.
Fun note: several of these releases are days old. You also share fixes with each other: tonyd2wild’s RDMA patch is what got bertholomus’s engine running on our network, and @majewskizby’s MTU fix landed in Mia’s recipe this morning. You’ve made a model this size practical to run on four desktop boxes, and our CVE work now runs on it - thank you!
August 2026: 12,275 CVEs published in one month.
That's almost double the 12-month average of 6,256, and the average is climbing too.
If your triage process was sized for 2023 volumes, it's already underwater.
The fastest-growing bug class since 2023 is missing authorization: code that works fine but never checks who is asking.
613 of those CVEs in August alone.
That's also when AI coding tools went mainstream.
Coincidence is doing a lot of work here.
exploit-intel.com/stats
Exploit Intel retweeted
I have found a few bugs and exploits in my time. I was once threatened with legal action, another time after much following up said company informed me that it wasn’t a bug. It was fixed in their next patch.
Everyone who I know that finds exploits has the same stories.
Exploit Intel retweeted
This is *quite* a post.
I honestly don't know offhand: Has Microsoft as a company ever before suggested in any official statement that it might seek to have criminal charges brought against security researchers who drop 0days?
microsoft.com/en-us/msrc/blo…
And while I've got your attention, patch your VMWare Fusion - CVE-2026-41702. exploit-intel.com/blog/posts…
We just released a Hermes Agent "Exploit Intel Harness" which turns Hermes into your Personal CVE vulnerability research assistant. This is a "diet" version of our forge tools - Check it out - exploit-intel.com/blog/posts…
CVE-2026-4105 - local root on systemd-machined. Two D-Bus calls, no auth. Fed it to CVEForge, had a working exploit in 72 minutes - then it found a bypass: exploit-intel.com/blog/posts… #CVE20264105
Back in the day we had milw0rm and a dream. Now it's 370K vulnerabilities, 92K with known exploits and growing. We're proud to finally hit the green button on our Exploit Intelligence Platform. Still early, still rough — but the foundation is real. exploit-intel.com/?v=2
