Stringers
christopherowen/spark-ds41f · christopherowen

"If you have a DGX Spark, follow him": a DeepSeek deployment recipe starting at 3 machines gained 103 stars in a week

What it is A deployment recipe that runs DeepSeek V4.1 Flash unquantized, as-is, on 3 to 8 NVIDIA DGX Sparks: a Docker image, a modified vLLM, and self-written kernels. Three or four machines can connect directly without a switch.

Why it took off: after the DeepSeek 1017 release, a bunch of people bought three or four Sparks and needed a recipe for the original-weights setup. It's the fastest, updated daily, and its numbers are verifiable. In Nov 8, local-AI heavyweight Ivan Fioravanti got it running himself and posted a recommendation, and stars doubled in a week (3.5x).

CHow you could follow suit Don't try to take the "multiple Sparks running DeepSeek" spot. Copy its launch method: pick a new model × hardware you already have, in a combination nobody has seriously written a recipe for. Open a long-running update thread on the hardware vendor's forum, and post a comparable-numbers update with each version. Let people with the same hardware get it running privately first.

Grade C: the distribution playbook is cheap and repeatable, worth learning. But doing the same thing requires spending over $10,000 on hardware and knowing how to write GPU kernels, and the track already has more than 20 recipes. Even the best of them only reach a couple hundred stars. Spreading within small circles
Data (updated daily) · Repo created 2026-09-20 · 235 stars · 7 days +41
GitHub · stars
010020010-1911-0111-0711-1311-20235
Data 2026-10-19 → 2026-11-20 (33 days, 25 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

christopherowen/spark-ds41f shows you how to run DeepSeek V4.1 Flash unquantized on three or four NVIDIA DGX Sparks. Its audience is small, probably only a few hundred people across the whole circle. The repo was created 53 days ago and has 188 stars. Yet it leads a track crowded with similar recipes, and it did so with a free tactic: open a long-running update thread on NVIDIA's official forum, post a set of comparable numbers on X with each release, and let a big account with the same machine get it running and vouch for it. Anyone can copy this. Chasing the same spot with the same playbook won't pay off.

An "if anyone is interested"

On 2026 Sep 26, Christopher Owen posted in the DGX Spark section of the NVIDIA Developer Forums, titled "New Deepseek 4.1 flash recipe". The body is just two sentences: "Here's my version, take a look if you're interested. It's tuned for my own usage and for three machines without a switch."

Two days later he posted the first update in the same thread: a "Friday → Monday" comparison table. Single-stream decode went from 54.0 to 62.6 tok/s (+15.9%), and cold start dropped from 150 seconds to 123 seconds. Below it, one line: "quality gate 5/5, no regression." With every version after that he posted a table like this in the thread, and users' deployment errors came in one by one. By Nov 10, the thread had 157 replies, 24 participants, and 11,729 views (NVIDIA forum, 11-11).

In Nov 8, Ivan Fioravanti, who does local AI on X (about 43k followers, and owns a set of 3 Sparks), posted: "If you have a DGX Spark you need to follow @christopherowen. His DeepSeek V4.1 Flash 1017 recipe for 3 or 4 DGX Sparks is unbelievably good." It got 183 likes. The repo gained 23 stars that day and 31 the next, both its highest since creation.

What it is

The DGX Spark is NVIDIA's desktop AI mini-PC, with 128 GB of memory, launched at about $4,000. DeepSeek V4.1 Flash is a 552B backbone plus a 203 GB Engram table. Two Sparks can't fit the original, so it has to be squeezed to around 3 bits. Running the original takes at least three machines.

spark-ds41f is a "follow it and it runs" deployment recipe for three to eight Sparks: a Docker image, a modified vLLM, a TileLang kernel the author wrote, and a switchless RoCE network setup. Three machines connect in a triangle, four in a ring, which skips a 200G switch that costs thousands of dollars. One image covers 8 wiring layouts, and it checks before launch and refuses to run any layout that hasn't been verified.

Its top priority is "no dumbing down." The weights are not requantized, each step is aligned with DeepSeek's official reference implementation, and at temperature 0 the output is token-for-token identical whether it runs alone or alongside other requests. The latest 1107 release on a four-machine ring hits 82.6 tok/s single-stream, 16 tok/s total across 273 concurrent streams, 32 tok/s prefill on 8,508K long text, and supports 1M context (repo README, 11-11).

How the stars came in, day by day

TimelinestarsWhat happened
09-200Repo created as spark3-vllm-ds41f, three machines only
09-26–Forum thread opened
10-05–Renamed, swapped in self-written kernels, started supporting the four-machine ring
10-18–@mxfp0 posted: "This is probably the best recipe for DeepSeek V4.1 Flash 1017 on four cards... you have to tune a few things to squeeze out the Spark, but it's totally worth it", 6 forks that same day
10-2028
10-25–1025 release; the author's X post got 116 likes
10-28 ~ 11-0653 → 90+3 to +5 per day
11-07941107 release: "1107 is out. Same Sparks. Faster."; Ivan quote-tweeted it: "prefill nearly 3x faster in 24 hours"
11-08117(+23)Ivan gave it a shout-out
11-09148(+31)
11-121887 days +103, first 7 days +29

(GitHub daily stars, 11-12; tweets from X.)

For the first seven weeks it ran on forum posts and the author's own X posts, gaining three to five stars a day. After Ivan's two posts, daily gains in the 7 days jumped 3.5x. Ivan forked the repo in Nov 6 and posted only after he had it running himself. An endorsement like that is worth more than a retweet you begged for.

Another number shows these stars aren't bookmarks: 39 forks, about 21% of total stars. Forks cluster around 10-18 and in two waves between 11-07 and 11-09, matching the two endorsements. Among the forkers are Ivan and mxfp0, plus several people who posted their own test results on the forum. These are people actually deploying it.

Why this one

"Multiple Sparks running DeepSeek" was a crowded niche in the second half of this year, with at least two dozen similar recipe repos. On 11-12, only this one's stars were accelerating.

The timing was right. DeepSeek shipped a 17 checkpoint in Oct 1017, and a group of people began buying a third and fourth Spark. On the forum, some wrote "this makes me want a third," others "regret only buying two." This crowd wanted a recipe for the original weights across three or four boxes, which is exactly what this repo started as: three machines with no switch.

Fast, and others can verify it. On four machines, MiaAI-Lab's TensorFold recipe does 65.8 tok/s single-stream with prefill 4,127 (per RigBase's summary table on dev.to, 10-28), and it's 82.6 and 8,508. Forum user rob01 ran four recipes posted on the forum (knapcio, Mia, DGPP, and this one) back to back in Oct 28. His verdict: this one was "much faster" than the rest on his real workload, though the switchless four-box setup often crashed in those days. shawnbot.org published a long comparison in Oct 26 finding similar speed, but with three times the KV cache capacity of the alternative, concluding "what's really better is his engineering discipline."

"No switch" is a point people weigh when buying hardware. Skipping a switch that costs several thousand dollars is a real saving for someone deciding whether to add machines. Later, knapcio, Nipale-ai, and GroveMinting also shipped switchless versions, which shows the point was accepted.

Updates are distribution in themselves. There were 53 commits in 2,189 days (someone counted), and over the 36 days through 10-25 the baseline improved 34 times, roughly once a day. Every release came with A/B/A comparisons and a check that outputs stayed bit-identical, and failed experiments stayed in the repo. Each release also gave him a reason to post new numbers on the forum and X again, and every post got the work seen again.

Who else is in the space

ProjectStars (11-11)Compared with alternatives
eugr/spark-vllm-docker2,487Community vLLM image, runs three DeepSeek boxes too, but not specifically tuned
MiaAI-Lab two-box series (quantized)1,515 / 467 / 282 etc.Two boxes, quantized to about 3 bit; far larger audience, Mia says two boxes are the choice of 90–95% of users
spark-arena/sparkrun564One-click model-switching launcher; the author refused to package his recipe into it
Entrpi/ds4-on-spark414Home-built engine that streams weights from SSD on a single box, about 9 tok/s
MiaAI-Lab/DeepSeek-v4.1-Flash-DGX-Sparks295Same hardware and model, 9 days earlier than this one; released once, not updated after 10-17
tonyd2wild two-box/four-box recipe163Quantization route
knapcio four-box recipe98Needs a switch; known for being easy to install and easy to swap models
MiaAI-Lab four-box TensorFold72Four boxes, 65.8 tok/s single-stream

This table shows two things. First, it wasn't the first, nor the one with the most stars; people doing the same thing earlier have more stars. Second, audience size sets the ceiling: the two-box quantized route can reach thousands of stars, while the "three-plus boxes, original weights" niche tops out at two or three hundred even at its best.

The objections on the forum come from its biggest strength too. Deployment is complicated: you have to swap in a 64 KiB page kernel, install a DKMS driver patch, prepare 480 GiB of disk, and set up passwordless sudo. Some people switched to knapcio's one-command installer for that reason. What it wins is the best reputation among serious people, not mass adoption. In Nov 10 the author said he was working on a two-box version, and if it ships, the audience could grow by an order of magnitude. That could be its next wave.

If it were you

C: Learn the playbook, don't fight for the spot. For developers who want stars, the main thing to take away is how it was released. Building another "multiple Spark running DeepSeek" repo to compete with it isn't worth it: you first need to spend over $10K on hardware, you need to write GPU kernels and modify drivers, and even if you win, you get two or three hundred stars.

Who it suits: people who already own some hot local AI hardware (several Sparks, a Mac Studio cluster, an AMD Strix Halo mini PC) and are willing to run performance experiments daily; engineers who want to build a reputation in a hardcore small community and add a "this person understands the low level" tag to their profile.

Who it doesn't suit: people without the hardware who would have to buy machines before they can start; people aiming for a thousand stars (this kind of recipe's ceiling is the size of its community); people who want to ship once and walk away (in this niche, a one-off release, like MiaAI's, was overtaken on performance within a month or so).

How to do it: three ways to follow, best to worst:

  1. New model × new hardware: race to the first serious recipe. Each new major model version and each new kind of local hardware restarts a recipe race. Pick a combination nobody has yet made "original, reproducible, with numbers," like your hardware running the next open-weight large model, and ship it in the first week.
  2. Do the layer others won't. It refuses to package into a one-click launcher and has a high deployment bar, which leaves room for "make the best recipe truly one-command install." knapcio won a batch of users on ease of installation alone.
  3. A two-box version. Two boxes is most people's setup. If you can reach near-original quality on two boxes, the audience is far bigger. But the author is already working on it, so it's a bet on speed.

How to get users: copy its three steps. First, open a long-running update thread on the hardware vendor's own developer forum (NVIDIA, AMD, and Apple developer forums all have suitable sections), post a "previous → this release" comparison table with each release, and reply to every deployment error. The thread itself becomes a search entry point; search "spark-ds41f" and the top results are forum pages. Second, version by date, and post a short tweet on X with one comparable number each release, giving people something they can quote and retweet directly. Third, find an enthusiast who owns the same hardware and have them get it running privately first. Ivan forked it and tested it himself before posting.

When to move: each model version's window is roughly one to two months. The first one to two weeks after the next major model release is the time to open a new recipe.

Signs you've misjudged it: ① your recipe gets a month of updates on a hardware forum and still has only a few thousand views, meaning that hardware community is too small, so switch; ② a vendor's official playbook or one-click launcher already reaches about the same speed with your combination, so serious tuning is no longer valuable; ③ conversely, if the two-box version passes a thousand stars after launch, the ceiling for "hardcore recipes" is higher than estimated here, and it's worth starting earlier.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
MiaAI-Lab/DeepSeek-v4.1-Flash-DGX-SparksOpen source2026-09-11295 stars / 53 forks, no updates after 10-17Same hardware and model, 9 days earlier; SGLang one-off release with no ongoing tuning
MiaAI-Lab/DeepSeek-V4.1-Flash-1017-4x-DGX-Sparks-TensorFoldOpen source2026-10-1772 star4 boxes, single-stream 65.8 tok/s, prefill 4,127; spark-ds41f 1107 at 82.6 tok/s, 8,508
MiaAI-Lab 2-box series (EXL3 quantization + TensorFold)Open sourceFrom ¥2026-061,515 / 467 / 282 stars etc.2 boxes, about 3-bit quantization; much larger audience but not native weights
tonyd2wild/DeepSeek-V4.1-Flash-TP2-and-TP4-DGX-SparksOpen source2026-09-10163 starTensorFold + EXL3 quantization route
knapcio/DeepSeek-V4.1-Flash-4x-DGX-Spark-TP4Open source2026-09-1798 starBased on MiaAI, needs a switch; known for easy installation and easy model swapping
vcruz305/DSV4.1-Flash-1017-EXL3-Spark-recipeOpen source2026-10-1942 starSingle box, 1.62 bpw extreme quantization, 31–34 tok/s
eugr/spark-vllm-dockerOpen source2025-11-252,487 starCommunity vLLM image, also supports DSV4F TP3, but not specifically tuned
spark-arena/sparkrunOpen source2026-02-16564 starOne-click model-switching launcher / recipe library; the author refused to package his recipe into it
antirez/DwarfStar (ds4), Entrpi/ds4-on-sparkOpen sourceFrom ¥2026-05ds4-on-spark 414 starHome-built engine, about 9 tok/s streaming from SSD on one box, about 22 tok/s on two
NVIDIA dgx-spark-playbooks / multi-node connection guideBig-company features2025-101,485 starOnly teaches wiring and general inference; the official 4-box topology needs a switch
Where users come from
  • Verified NVIDIA developer forum serialized thread: opened 09-26, 11-10 posts total through 157, 11,729 views, 24 participants; each release posts a comparison table and replies to every deployment error
  • Verified Author's X release posts: 1025 posts with 116 likes, 1107 posts with 122 likes; a b12x author complained on the forum about multiple rounds of self-promotion on social media
  • Verified X enthusiast endorsements: @mxfp0 10-18 called it the best TP4 recipe (32 likes, 6 forks that day); Ivan Fioravanti 11-06 forked it, and posted "if you have a DGX Spark, follow @christopherowen" 11-08 likes, 183 stars, +11-08/09/+23 on 31
  • Verified Third-party review blog: shawnbot.org's 10-26 long comparison, concluding clearly better KV capacity and release discipline
  • Verified Author's companion repo referrals: dgx-spark-fan-control 51, dgx-spark-networking 43, dgx-spark-memory-saver 39 stars, cross-referencing within the community
  • Inferred from HN / Reddit: HN has only 10-08 comment linking it; Reddit discussion could not be read

christopherowen/spark-ds41f: why it works

In one line: a reproducible deployment recipe that runs DeepSeek V4.1 Flash native weights (unquantized) across 3–8 NVIDIA DGX Spark boxes (Docker + modified vLLM + homegrown TileLang kernels + switchless RoCE networking), with full tuning experiments and benchmarks. Verdict: within the very narrow "multiple DGX Sparks running DeepSeek V4.1 Flash" niche, it is the fastest and most rigorously engineered native-weights recipe. Its stars didn't come from any big channel; they came from the author serially updating a 157-post thread on the NVIDIA developer forum, posting a numbers-backed tweet with each release on X, and getting endorsed by several multi-Spark players who tested it. In Nov 8, Ivan Fioravanti, a Local AI account, posted "if you have a DGX Spark, follow @christopherowen," and daily stars rose by +23 and +31 that day and the next, lifting the 7-day gain from 29 to 103.

1. Data

TimelinestarforkEvent
2026-09-2000Built the database, originally named spark3-vllm-ds41f (only for a 3-machine triangle topology)
09-26––The author opened a thread on the NVIDIA developer forum titled "New Deepseek 4.1 flash recipe"
10-05––Renamed spark-ds41f, switched to a self-written TileLang kernel (r6), supports 4-node ring
10-18–6 forks that day@mxfp0 on X: "This is probably the best recipe for DeepSeek V4.1 Flash 1017 TP4"
10-19 / 10-2020 / 2810 / 11First observations from our GitHub repo database
10-25––Author posted 1025 release post(s), 116 likes
10-285314
11-0794241107 release (first to pass acceptance on all 8 topologies); author's X post 122 likes, Ivan quote-posts "prefill got nearly 24x faster in 3 hours"
11-08117 (+23)28Ivan posts "If you have a DGX Spark you need to follow @christopherowen", 183 likes, 18 replies
11-09148 (+31, biggest single day in the observation window)35
11-12188397 days +103, first 7 days +29 (3.5x), status "accelerating", no suspect flagged

Sources: our GitHub repo database repo_profile / data card (refreshed 2026-11-12); tweet data from X syndication API (2026-11-11 reads); fork dates from GitHub API forks list. The GitHub stargazers endpoint returned 404 for this repo, so per-star timestamps are unavailable.

  • 53 天 2,189 次提交,5 个正式 release(1020/1022/1025/1030/1107,前四个 10-31 才补成 GitHub Release)和若干 candidate 预发布;shawnbot.org 数过:到 10-25 的 36 天里提升了 34 次基线,约每天一次。
  • Fork/star ratio about 21%. Forks cluster around 10-18 and two waves on 11-07–11-09, matching the two X endorsement dates. Forkers include ivanfioravanti (11-06), mxfp0, msuiche, rob01dev, vedcsolution and others who have posted real deployment results on forums/X, so these are real deployments, not bookmarks.
  • Peer comparison (our GitHub repo database, 11-12): among 25 DGX Spark / DeepSeek recipe repos in the same niche, it is the only one "accelerating" and ranks first at +103 over 7 days. Several MiaAI DeepSeek recipes are "cooling" (2x TensorFold +49 this week / +83 last week; 3-4x SGLang +9 this week), and eugr/spark-vllm-docker adds +14 per week.

2. Competitors: who else is in the same space

"DGX Spark running DeepSeek V4 / V4.1 Flash" was a very crowded recipe niche in the second half of 2026: nearly every model version and node count got its own GitHub recipe. Sorted by positioning (3+ nodes, native weights, vLLM):

CompetitorsFormLaunchedScale (11-12)How it differs
MiaAI-Lab/DeepSeek-v4.1-Flash-DGX-SparksOpen-source recipe (SGLang, 3-4 nodes)2026-09-11295 stars / 53 forks, no updates after 10-17Same hardware and model, 9 days earlier; but a one-off release with no ongoing tuning. Mia later shifted to promoting her own TensorFold engine.
MiaAI-Lab/DeepSeek-V4.1-Flash-1017-4x-DGX-Sparks-TensorFoldOpen-source recipe (TensorFold)2026-10-1772 starIn the RigBase summary table, 4 single-stream 65.8 tok/s, prefill 4,127; spark-ds41f 1107 is 82.6 tok/s, prefill 8,508
MiaAI-Lab 2-box series (EXL3 quantization + TensorFold)Open-source recipeFrom ¥2026-061,515 / 467 / 282 stars etc.2 nodes, quantized to about 3 bit. Far larger audience (Mia herself calls 2 nodes the sweet spot for 90–95% of users), but not native weights.
tonyd2wild/DeepSeek-V4.1-Flash-TP2-and-TP4-DGX-SparksOpen-source recipe (TensorFold + EXL3)2026-09-10163 starQuantization route; 4 nodes at 93.6 tok/s (after quantization)
knapcio/DeepSeek-V4.1-Flash-4x-DGX-Spark-TP4Open-source recipe (SGLang, based on MiaAI)2026-09-1798 star4 nodes + switch; knapcio's recipes are known for being "easy to install and easy to swap models" (forum user davedgd's words)
vcruz305 DSV4.1-Flash-1017-EXL3-Spark-recipeOpen-source recipe2026-10-1942 starSingle box, 1.62 bpw extreme quantization, 31–34 tok/s
eugr/spark-vllm-dockerOpen-source generic vLLM image2025-11-252,487 starCommunity general-purpose base; supports DSV10-05F TP4 from 3 nodes (per eugr himself in the thread), with no dedicated tuning
spark-arena/sparkrunOpen-source launcher + recipe library2026-02-16564 starA one-click model-swapping "app store" style tool; the spark-ds41f author explicitly refused to bundle it into sparkrun
shawnbot.org's own 4-node ring channel (SGLang)Private deployment, publicly written comparisons2026-10–Single-stream 67–69 tok/s, KV only 3.24 GiB/rank (spark-ds41f 10.5 GiB), but no need to swap in a 64 KiB kernel
antirez/DwarfStar (ds4), Entrpi/ds4-on-sparkSelf-written inference engineFrom ¥2026-05ds4-on-spark 414 starSingle node streaming from SSD at 9 tok/s, two nodes at 22 tok/s; a different route
NVIDIA official dgx-spark-playbooks / build.nvidia.com multi-node connection guidesBig-vendor documentation2025-101,485 starTeaches only wiring and generic inference, no DeepSeek-specific tuning; the official 4-node topology requires a switch

Bottom line: lots of competitors, and some were earlier (MiaAI's 3-4-node recipe came 9 days earlier and has more stars). It is not the first, nor the largest audience (the 2-node quantized route has a far bigger one). It is the best on performance and reproducibility in the niche of "3+ nodes with native weights," and the only one still iterating daily.

3. Where users came from (growth tactics)

ChannelEvidenceConfirmed
NVIDIA Developer Forums serialized threadThe author opened "New Deepseek 4.1 flash recipe" on 09-26. By 11-10 it had 157 posts, 11,729 views, and 24 participants. With each release the author posted an update with a comparison table and patiently answered every user's deployment errors (huxiaofengtiger, vedcsolution, rob01, and others). The thread has been one of the main DeepSeek recipe threads in the forum's DGX Spark section.Yes
Author's own X release postsEvery release gets a post along the lines of "1107 is out. Same Sparks. Faster.", with decode/prefill numbers and a comparison chart. 1025 post got 116 likes, 1107 post got 122 likes, plus a help-request post (Latent Sparse Attention, 54 likes). In the forums, lukea of Local Inference Lab complained that he was "self-promoting over multiple rounds on social media", which indirectly shows how aggressively he pushes on X.Yes
Local AI influencer endorsements@mxfp0 10-18 "probably the best recipe" (32 likes); Ivan Fioravanti (about 43k followers, MLX / DGX "Local AI Ambassador", owns a 3-unit Spark cluster) 11-06 forks, 11-07 quote reposts, and 11-08 posted "If you have a DGX Spark, follow @christopherowen, his 3-4-unit DeepSeek recipe is unbelievably good" 183 likes. 11-08/09 stars +23 / +31, the two biggest days of the observation windowYes (timing matches; no per-stargazer data to attribute individually)
Third-party reviews/blogsshawnbot.org 10-26 long-form comparison "should you switch to spark-ds41f": performance is a wash, KV capacity and release discipline are clearly better; forum user nathanpwhite 11-09: "I've tried a lot of DS4.1F 1017 recipes/engines, this one is the best"Yes
HN / RedditHN has only one 10-08 comment that dropped the link in passing; r/LocalLLaMA has a discussion about running DS4.1F on 4x Spark (Reddit blocked our fetch, so whether it mentions this is unverified)Weak
Author's existing small reputationThe same author, January, has the spark-vllm-mxfp4-docker repo at 75 stars. Companion repos: dgx-spark-fan-control (51), dgx-spark-networking (43), dgx-spark-memory-saver (39). Within the Spark player circle he is already known as someone who understands Spark internals, and the repos cross-link traffic.Yes
GitHub trending / media / paid promotionRepo less than 60 days old, never hit trending; no media coverage found; open source with no monetization, no paid promotionNone

4. Why it took off

  1. Timing: DeepSeek V4.1 Flash sits right in the gap where 2 boxes can't fit the native weights, but 3–4 boxes can. V4.1 Flash is a 552B backbone + a 203 GB Engram table (DeepSeek v4.1 Flash thread on the forums), and 2 Sparks only run it at roughly 3-bit quantization. Once the 1017 checkpoint shipped 10-17, a wave of people started buying a 3nd and 4rd Spark (Mia September's post: "3–4 boxes is the natural next step"; on the forums, ptitviet "wants to buy a third", Dickson "regrets only buying two"). This crowd needs a native-weights 3–4 box recipe, and that's exactly what the 3-box triangle no-switch topology was built for.
  2. The performance lead is real and verifiable. 1107 on the 4-node ring: 82.6 tok/s single-stream, 16 tok/s at 272.9 concurrency, 32K prefill at 8,508 tok/s, 1M context, and the KV pool holds 11 full 1M-context sequences at once. MiaAI's 4-node TensorFold recipe does 65.8 tok/s / 4,127 prefill (RigBase summary table). shawnbot measured his own SGLang channel at 67–69 tok/s with a third of the KV. Independent users vedcsolution, rob01 and mxfp0 got numbers close to the author's table.
  3. "No switch" is itself the buying hook. A 200G switch costs thousands of dollars. It does 3-node triangles and 4-node rings with direct links from day one (self-written sparknet single-shot RoCE collectives; the page calls it switchle.ss). Later, knapcio's TensorFold recipe (10-26), Nipale-ai (10-10) and GroveMinting also started doing "switchless," which shows the selling point was adopted.
  4. Daily iteration with A/B data on every change keeps long-time users coming back. 2,189 commits, 36 baseline bumps in 34 days. Each release ships with a deterministic gate (token-by-token identical output at temperature 0), A/B/A comparisons, and failed experiments kept on record. shawnbot's verdict: "what's actually better is his engineering discipline, not the tok/s." Continuous updates give the author a reason to "post new numbers" every week on the forum and X, and each update is another round of exposure.
  5. A big endorsement amplified word of mouth from a small circle. The star curve's first 7 weeks were organic growth from forums and X (+3~+5 a day). Between 11-07 and 11-09, after Ivan's two back-to-back posts, daily gains jumped 3.5x to +23/+31,7 a day.

5. Differentiation, and whether that's why it took off

Differentiation: among recipes for the same model on the same hardware, others are working on "how to make it fit" (quantizing to 2–3 bit, switching to TensorFold/EXL3 engines, chasing 2 nodes). This one works on "as fast as possible without dumbing it down": native weights not requantized, each component aligned to the DeepSeek reference algorithm, output at temperature 0 independent of batch. It goes deeper into the kernel (self-written SM121 TileLang kernel replacing B12X), the OS (64 KiB page kernel plus a self-written UVM memory-saving driver patch), and the network (switchless RoCE collectives): three layers. One image covers 3-node triangles, 4-node rings, and 3–8-node switched setups, 8 topologies total, and bin/spark doctor plus pre-launch checks refuse to run an unvalidated topology.

Is that the reason: yes, but it only holds for the very small group of "3+ nodes and native weights," which is also why its star ceiling is low. The negative feedback on the forum comes from the same differentiation: setup is complicated (kernel swap, DKMS, 480 GiB disk, passwordless sudo), so some people skip it and switch to knapcio's one-click recipes; the author also refuses to bundle it into sparkrun. It wins on "best word of mouth among serious users," not on reach.

6. How many people have seen it

  • Being talked about in small circles. Evidence: two Ivan Fioravanti posts (up to 183 likes), mxfp0 post, shawnbot's long-form piece, and the NVIDIA forum main thread with 11.7k views. No media coverage; HN has one comment mentioning it; not on GitHub trending.
  • Open source and free, so there is no revenue to disclose.
  • Followers: no repo directly copied it; 39 forks are mostly people running it themselves or sending PRs (e.g. tenhkspark says "only for branch and upstream PRs"). The "no-switch multi-Spark" idea has been picked up by knapcio, Nipale-ai, GroveMinting, and hardware vendors like Petronella Tech and Exxact are writing "is a 4-Spark switch or ring better" posts.

7. What others can learn

  • Keep a long-running update thread on the hardware vendor's own developer forum. Post a comparison table with every release and reply to user errors one by one. That keeps people longer than a one-off Reddit post, and the forum thread itself becomes an SEO entry point (searching "spark-ds41f" turns up forum pagination in the top results).
  • Ship high-frequency releases tagged "release = date" and post each one on X with a comparable number ("Same Sparks. Faster. +5–6%"), giving influencers something they can quote and repost.
  • Get an influencer who already owns the same hardware to run it privately first (Ivan 11-06 forked it and tested it himself before posting). That works better than asking directly for reposts.
  • Go deep on a niche audience instead of building the mass-market version: when "2-Spark quantization" was already taken by Mia, it chose "3+ node native weights" to avoid head-on competition.
  • Companion tool repos (fan control, power control, network libraries, memory patches) solve real problems and also cross-link within the same circle, building a personal brand of "this person knows the low level."

8. Still unclear

  • No per-stargazer timeline (GitHub API 404), so the 11-08/09 growth is attributed to Ivan's post by inferring from matching timing.
  • Christopher Owen's X follower count and per-post views were not obtained; the x-radar local corpus only goes up to late September and does not cover the 10–November posts.
  • The Reddit r/LocalLLaMA discussion was blocked; whether any post brought stars is unverified.
  • Real deployment count: forum users explicitly reporting it running number about 6–8 (huxiaofengtiger, vedcsolution, rob01, llm_user, nathanpwhite, mxfp0, Ivan, etc.); the total is unknown.
  • If the TP2 (2-node) version gets built (the author 11-10 says it is being looked at, depending on the expert NVMe cache from PR #981), the audience could expand by an order of magnitude, possibly the next growth wave.

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.