A 1100-star GPU-mixing experiment repo: the topic is real, the stars were bought
What it is An experiment log for heterogeneous GPU inference: it uses 3080, 6000D-class discrete GPUs to offload large-model inference from high-memory hosts like 395 and DGX Spark, publishes speed tests, and keeps the key patches private.
Why it blew up The topic hits a real pain: in 2026, unified-memory mini PCs can hold big models but read long inputs slowly. The packaging looks polished, but most of the stars were bought in daily batches by paid accounts, not organically spread by the community.
CHow you could ride it Do what it deliberately left out: a fully open, one-command mixed setup, starting from the 3060/3080 + 395 tier. Post it on r/LocalLLaMA and Bilibili, and ideally get it merged into llama.cpp or exo.
- Data (updated daily) · Repo created 2026-09-01 · 1,137 stars · 7 days +101
GitHub · stars Data 2026-10-09 → 2026-11-08 (31 days, 30 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
Soulmate-Halo/heterogeneous-gpu-pd-lab is one Chinese developer's experiment log. It pairs high-compute discrete GPUs like the RTX 3080 and RTX 6000D with big-memory, weaker-compute hosts like the AI Max+ 395 and DGX Spark, to speed up local LLMs. It gained 1,112 stars in 66 days and looks like a small hit in the local-LLM crowd. But the stars are suspicious: almost nobody discusses it off-platform, and the repo reads more like a storefront for the author's GPU rental site. The topic is real and worth understanding; copying its growth playbook is not.
An issue nobody answered
On 2026 Oct 27, a user named tokamaktt opened issue #6 under this repo. They had read the Chinese deployment doc for DeepSeek-V4.1-Flash V10 closely, sections 2, 3, 4, 7 and 12, and asked five things in one go: who supplies the dsv41-pd-package-20261013 delivery package the doc mentions; how the fp4h96 model format gets generated from the official weights; whether the 21 vLLM patches of P35 are planned to be released; whether the full SGLang source and Dockerfile can be shared; and, if they can't, whether a technical write-up is available instead.
By Nov 6 the author still hadn't replied. The only follow-up was one line from another account in English: "I want this info too, thanks!"
A day earlier, on Oct 26, another user, Lwan12, asked: "We plan to reproduce the README's recommended setup: 4 DGX Spark for Decode and 2 RTX 6000D for Prefill." They wanted to know which switch to buy and which RoCE settings to enable. No reply either.
These two posts are the most telling things in the repo: someone really wants to replicate this, and is ready to spend tens of thousands on hardware. What blocks them is exactly the part the README says stays private.
What it actually is
LLM inference runs in two steps: first it reads your whole input (prefill), then it generates output one token at a time (decode). In 2026, many people got machines with 128GB of unified memory: AI Max+ 395 mini PCs, NVIDIA's DGX Spark, 512G Macs. They can hold big models, but reading long inputs is slow. The repo's idea: plug in a discrete GPU to handle the "reading" and let the big-memory host handle the "writing," or keep the frequently used parts of the model on the GPU and the rarely used parts on the host.
The README opens with a 12-minute, 22-second explainer video (one version with Chinese voiceover, one with English), followed by a stack of benchmark tables. The most eye-catching numbers (self-tested by the author, per the README, 11-06):
| Setup | Model | Result |
|---|---|---|
| RTX 3080 20GB + AI Max 395 | Qwen3.8 Flash-Next | Prefill rose from 273 to 844 tok/s, about 3.1x; decode barely changed |
| RTX 3080 + DGX Spark | Qwen3.8 Flash-Next | Single-stream decode rose from 22.3 to 62 tok/s |
| 2×RTX 6000D + 4×DGX Spark | DeepSeek-V4.1-Flash | Prefill of 32K-token input at 16,000+ tok/s |
Every section ships a Docker image and deployment notes, which looks serious. But a closer read shows the images "contain no weights and no private role images," and the 130GB vendor package and those 35 patches aren't in the repo. All 252 commits come from the author alone.
Where the 1100 stars came from
Look at the curve. On Oct 16 it had 794 stars; by Nov 6 it had 1,112, gaining 10 to 22 a day, almost a straight line, with a single-day peak of 22 (10-10). Over the last 7 days it gained +107; the 7 days before that, +123. Forks follow the same pattern: 84 in September, 76 in October, and 15 in the first 5 days of November, a steady drip. It has never appeared on GitHub Trending.
Repos that people genuinely share don't look like this. A single big account repost leaves a spike. This one has no spikes at all.
Now look off-platform. Nearly 60 days of searches for the repo and author names on X turn up zero posts; Reddit, Hacker News, Zhihu, and V2EX return nothing. The only hits are a few aggregator sites that scrape GitHub. On Bilibili there's a related video, "AI观模者"'s Sep 26 post "GPU prices soaring? Unified memory + discrete GPU heterogeneous acceleration is here!", with 12.9k views, but I couldn't find it linking to this repo (I didn't verify whether the video mentions it).
Finally, look at who forked it. Of the 175 fork accounts, 161 were registered 2025 years ago, 107 have no more than 3 followers, and in a typical account's public repos 96% are forks (median). Pulling what the top 80 accounts forked recently: they jointly forked a batch of unrelated Chinese projects, including hyperai/tvm-cn (17 accounts forked it), TJU-DRL-LAB/AI-Optimizer (14), dataelement/bisheng (12), HKUDS/LightRAG (12)... None of the top 30 is a local-inference library like llama.cpp, vLLM, or exo.
Compare that with two repos on the same topic: the fork accounts of strix-halo-llamacpp and ik_llama.cpp jointly forked llama.cpp, exllamav3, and BitNet, which is what people who actually run local inference fork.
So the conclusion: the forks come from a pool of paid accounts, dripped out steadily each day, and the stars very likely do too (inference; high confidence; I couldn't directly verify the list of starring accounts).
So what's the payoff?
The author's account was registered in Aug 2026 15, with a one-line bio: "I want to go down in history." He has only two repos; the other is a desktop client called 器灵 Soulmate, with 139 stars and 2 forks.
The real destination is qlsoulmate.com, called "器灵算力站" (Soulmate Compute Station). The homepage has "Rent" buttons for the DGX Spark and RTX PRO 6000, plus a token store (model APIs settled in RMB), a secondhand GPU market, and a hardware guide, with "rent or buy calculator" and other "phase two" features queued up. The homepage links to this repo and shows a QR code for a "model setup discussion group." As of Nov 6, the rental and hot-model leaderboards still say "Loading…", so rental volume and revenue aren't visible from outside.
Put these together and the path is clear: the public part makes the case that mixing hardware is worth it, the key patches stay private, and anyone who wants to reproduce it has to join the group, rent machines, or hire the author to deploy. The 1100 stars exist to look credible in GitHub search and aggregator sites.
Who was already doing this
| Project | Stars | Compared with alternatives |
|---|---|---|
| exo | 48k | In October 2025 it published a blog post, "DGX Spark + M3 Ultra Mac Studio is 4x faster": Spark reads, Mac writes, built into an automatic feature in software you can use right away |
| llama.cpp | 133k | Native multi-GPU and multi-machine layer splitting; this repo's patches are built on top of it |
| ktransformers | 19.7k | CPU memory holds the experts and GPU computes attention, aimed at servers |
| ik_llama.cpp | 3,400 | Hybrid CPU/GPU offloading for MoE |
| Mooncake / NVIDIA Dynamo | 7,000 / 8,500 | Datacenter-grade read/write separation on homogeneous clusters |
| gpustack / distributed-llama | 6,000 / 3,100 | Heterogeneous device cluster management and multi-machine inference |
| strix-halo-llamacpp | 224 | Only tunes single-machine 395 |
Add to that the many free, reproducible setups on the NVIDIA forums and r/LocalLLaMA: two Sparks running DeepSeek, Spark plus Mac, and so on. That discussion is far bigger than this repo's. What really sets it apart is just one thing: it's in Chinese, targets cards you can buy in China (used 3060/3080 and the China-specific 6000D) and mixes them with 395 and Spark, and has more benchmark tables.
If it were you
One-line verdict: The topic is worth borrowing, the playbook is not. "Cheap discrete GPU + big-memory host" is a real problem for local-LLM users in 2026, but this repo's stars were bought, so they don't prove the topic can earn 1000 stars organically. exo got there a year earlier, shipped software, and has a big account backing it.
Who it's for: People who actually own a 395, a Spark, or a big-memory Mac, plus one or two discrete GPUs, and who will publish every step. Also people who want to build a name in the Chinese local-inference community.
Who it's not for: People without the hardware who can only write docs, and people hoping to buy stars as a storefront to drive traffic. Bought stars don't earn Trending placement or discussion, and in 66 days this repo drew only 3 external issues.
How to do it: Build the part it deliberately left out, fully open and runnable with one command. The smallest entry point is the 3060/3080 + 395 tier, a few thousand dollars in hardware, which the most people can afford: write ready-made layer-split scripts and configs for llama.cpp, one page per hardware combo, with reproducible benchmark scripts and raw logs. If you can turn "GPU reads, host writes" into a plugin or PR for llama.cpp or exo, that gets seen far more easily than a standalone repo.
How to get attention: Post the first piece on r/LocalLLaMA and the NVIDIA developer forum's Spark section, with the hardware combo and the multiplier right in the title ("One 3080 makes 395 prefill 3x faster, fully open source"). For Chinese audiences, post on V2EX, Zhihu, and Bilibili, and reach out to UP hosts like "AI观模者" who already cover this topic. Bring the results into llama.cpp's discussion board and get one mention from a main-repo maintainer. That's worth more than a hundred bought stars.
Window: The 395 and Spark wave is still ramping up. Finish before the next generation of unified-memory machines ships; that's roughly a six-month window (inference).
Signs you've misjudged it: If the post gets no replies on Reddit two weeks after launch and stars stay in the double digits, that means fewer people than you think will tinker with mixed hardware. Or, if exo or llama.cpp upstream adds this kind of mix as a one-click feature first, a standalone config repo stops being worth anything.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one exo Open source 2024-06 (PD separation 2025-10 blog) 48.2k star exo already ships "Spark does prefill, Mac does decode" as an automatic feature in EXO 1.0, backed by a big account. This repo is just a benchmark log plus some patches, aimed at Chinese users and consumer hardware mixes. llama.cpp(RPC/tensor split) Open source 2023 133k star General multi-GPU, multi-machine layer splitting; this repo adds patches and tuning on top for PD division between discrete GPUs and unified-memory hosts. ktransformers Open source 2024-07 19.7k star CPU memory holds the experts and GPU computes attention, aimed at servers; this repo targets 395/Spark. ik_llama.cpp Open source 2024-06 3.4k star Hybrid CPU/GPU offload optimization for MoE, with no cross-device PD separation. Mooncake / NVIDIA Dynamo (paired with vLLM/SGLang) Open source 2024-06 / 2025-03 7.0k / 8.5k star PD separation on datacenter homogeneous clusters, not aimed at home hardware mixes. gpustack / distributed-llama Open source 2024-05 / 2023-12 6.0k / 3.1k star Heterogeneous device cluster management and distributed inference, without prefill/decode division tuning. NVIDIA forum and Reddit r/LocalLLaMA setup posts Other 2026 Plenty of free posts Two Sparks running DS4 Flash, Spark plus Mac, and similar setups: free and reproducible, with far more discussion than this repo. - Where users come from
- Inference Paid star/fork farming (account pool): of the 175 fork accounts, 161 were registered 2025 years ago; median fork share 96%; the top 80 accounts jointly fork a batch of unrelated Chinese projects (hyperai/tvm-cn 17, AI-Optimizer 14, bisheng 12, zhnt/loushang 10, kpleo/pyraimd 7), and none of the top 30 is in the llama.cpp ecosystem; control repos strix-halo-llamacpp and ik_llama.cpp have fork accounts that jointly fork llama.cpp, exllamav3, and similar; stars and forks grow at a steady daily rate with no spikes
- Confirmed Traffic funneled to the author's commercial site: qlsoulmate.com (器灵算力站: GPU rental, token store, secondhand GPU market) links to this repo and shows a QR code for a "model setup discussion group" on its homepage
- Confirmed Content packaging (bilingual README + 12-minute explainer video + benchmark tables): the README embeds a v24 Chinese/English voiceover video, with a 1080p source file in releases; 252 commits, updated frequently
- Inferred Bilibili video on the same topic: "AI观模者" (15.7k followers) 2026-09-26 "Unified memory + discrete GPU heterogeneous acceleration is here" 12.9k views. No link to this repo was found on the page.
Soulmate-Halo/heterogeneous-gpu-pd-lab research report
Research date 2026-11-06. Sources: data card (GitHub repo, daily stars/forks from 2026-10-16 to 11-06), GitHub REST/GraphQL API (live as of that day), Jina/Exa web search, x-radar (X corpus).
Bottom line
This is the heterogeneous GPU inference lab notebook of a Chinese indie developer, "Halo / Halo-lab 光环实验室". It uses compute-strong discrete GPUs like the RTX 3060/3080/6000D to split prefill/decode work for memory-rich but compute-weak machines like the AI Max+ 395, DGX Spark, and M3 512G. The topic hits a real pain point for local LLM users in 2026, but it has essentially not been picked up by the community: 1100+ stars with almost no discussion off GitHub, and its 175 forking accounts show clear signs of a bot-account pool. The repo works more as a lead-gen front door for the author's commercial site qlsoulmate.com (器灵 compute rental: GPU rental, token sales, used-card sales) and the desktop client "器灵 Soulmate".
1. Basic data
- Created 2026-09-01,66 days ago; stars 1112 (data card) / 1120 (API, same day), forks 175, watchers 113, only 5 issues (2 of them are the author's own video posts).
- Growth curve: 10-16 at 794 → 11-06 at 1112, about +10 to +22 per day, a very smooth straight line, peak single day 22 (10-10), last 7 days +107, first 7 days +123. Never on GitHub Trending (trending_days_any=0). The third-party aggregator ai427.com caught "796 Stars" early on.
- Fork timing: September 84, October 76, first 5 days of November 15. Again a steady drip with no spike from some big account reposting it.
- Repo content: bilingual Chinese/English README, a 12-minute explainer video (Chinese/English voiceover), many benchmark tables (3060+395 on 9B models with prefill +34%/+120%; DS4.1 Flash on 2×6000D + 4×DGX Spark PD split at 16000+ tok/s prefill, etc.). After 2026-10-06 a reproducible package for qwen38-flash-spark-3080 was released (511 files). But the README states that "deployment commands, patches, endpoints, and layer allocation strategy remain private." All 252 commits come from one person.
- Author account Soulmate-Halo: registered 2026-08-15, bio "我想青史留名" ("I want to go down in history"), 160 followers, only 2 repos. The other is qiling-soulmate (器灵 Soulmate, a multi-AI-CLI orchestration desktop client), 139 stars, only 2 forks.
2. Competitors
| Competitors | Form | Launched | Scale | How it differs |
|---|---|---|---|---|
| exo(exo-explore/exo) | Open source | 2024-06 | 48.2k star | 2025-10 published the blog "DGX Spark + M3 Ultra Mac Studio = 4x faster", turning PD split (Spark for prefill, Mac for decode) into an automatic feature of EXO 1.0. That is the core idea of this repo. exo got there a year earlier and it is usable software; this repo is measured notes plus some patches |
| llama.cpp(RPC / tensor split / override-tensor) | Open source | 2023 | 133k star | Natively supports multi-GPU and multi-machine layer splitting, but has no prefill/decode tuning for the "discrete GPU + unified memory host" combo; this repo patches on top of it |
| ktransformers | Open source | 2024-07 | 19.7k star | Heterogeneous inference with MoE experts on CPU RAM and attention on GPU, targeting server RAM rather than 395/Spark |
| ik_llama.cpp | Open source | 2024-06 | 3.4k star | llama.cpp fork with optimizations for MoE hybrid CPU/GPU offload |
| vLLM/SGLang + Mooncake / NVIDIA Dynamo | Open source | 2024-2025 | Mooncake 7.0k, Dynamo 8.5k stars | Datacenter-scale PD split, mainly homogeneous clusters |
| gpustack, distributed-llama | Open source | 2023-2024 | 6.0k / 3.1k star | Heterogeneous device cluster management / multi-machine distributed inference |
| Nathanw1014/strix-halo-llamacpp | Open source | 2026-07 | 224 star | Tunes only single Strix Halo machines, no heterogeneous setups |
| NVIDIA forum, Reddit r/LocalLLaMA threads | Community | 2026 | A lot | Dual-Spark DS4 Flash runs, Spark + Mac Studio setup posts; free and reproducible |
Conclusion: this isn't an unexplored idea. exo has already turned the same idea into a product with big-account backing. This repo's difference is that it is in Chinese, aimed at consumer mixed hardware (3060/3080-class used cards + 395/Spark), with lots of measured tables and explainer videos.
3. Growth tactics: where the stars came from
3.1 Almost no organic spread off GitHub (checked)
- x-radar search for "heterogeneous-gpu-pd-lab" and "Soulmate-Halo" over the last 60 days: 0 posts.
- Jina/Exa search for the repo name: besides GitHub itself, the hits were only auto-scraping aggregators like ai427.com, papers.ananclaw.com, agentlenshq.com, beeknoee.com. Aggregators that auto-scrape GitHub. No mentions found on Reddit, HN, Zhihu, or V2EX.
- On Bilibili, "AI观模者" (15.7k followers) posted "High-end GPUs too expensive? Unified memory + discrete GPU heterogeneous acceleration is coming!" (12.9k views, 2026-09-26). The topic is highly relevant, but the page text has no evidence linking it to this library (unverified whether the video mentions it).
- The author has a link to this repo and a "model building discussion group" QR code on the homepage of their own site qlsoulmate.com.
3.2 fork accounts show signs of a bot-account pool (checked, strong evidence)
- Of 175 fork accounts, 161 were registered 2025 years ago (old accounts), 107 have ≤3 followers, and the median share of forks among their public repos is 96%, with a median of 220 stars given.
- Shared-fork analysis (top 80 fork accounts, looking at their last 50 forks): besides this repo, they heavily co-fork a batch of unrelated Chinese projects: hyperai/tvm-cn (17 accounts), TJU-DRL-LAB/AI-Optimizer (14), qualcomm/GenieX (13), hyperai/awesome-ai4s (13), OpenDCAI/DataFlow (13), yikart/AiToEarn (12), dataelement/bisheng (12), HKUDS/LightRAG (12), zhnt/loushang (10), kpleo/pyraimd (7)… Not one llama.cpp / vLLM / exo ecosystem repo appears in the top 30.
- Control group (55 fork accounts of strix-halo-llamacpp and ik_llama.cpp): they co-fork ggml-org/llama.cpp (12), exllamav3, BitNet, amd-strix-halo-vllm-toolboxes, etc., which fits the profile of people who actually run local inference.
- Spot-checked personal profiles: Vision33r, FeoNeo, petshit, widowmalay, Kempingski, HYCooNG and others have 100% of their repos as forks with 0 stars, and their fork timelines overlap heavily (they all forked loom, loushang, pyraimd and this repo within a few weeks).
- Judgment: the forks (and very likely the stars) come from the same pool of paid bot accounts, distributed evenly day by day. That matches the curve of "+10 to 20 per day, no spikes, never on trending." The stargazers list API was unavailable with our token, so the star accounts themselves could not be checked directly.
3.3 There is real demand, but it is small
- 3 external issues ask about specific hardware setups (4× Spark + 2×6000D: which switch to use; how to configure 1–2 Pro6000 cards + 2 Sparks; whether the V10 raw delivery package can be reproduced). So a few real players are watching.
3.4 Where the money comes back
- qlsoulmate.com "器灵 compute station": rent DGX Spark / RTX PRO 6000 machines ("body selection", "console/deployment"), a token mall (model API resale settled in RMB), a used GPU market, a hardware encyclopedia, and a "rent vs buy calculator". The homepage carries the repo link and the group QR code.
- qiling.swcbg.com "器灵 Soulmate" desktop client: multi-CLI orchestration, strong model plus weak model to save money.
- The repo makes the case that "heterogeneous acceleration is great" but keeps the key deployment commands and patches private. That steers people who want to reproduce it toward renting machines, joining the group, and paying for deployment. The star count is there to make the front door look credible.
4. Why it took off (why)
- The timing is right: in 2026 395-class 128GB unified-memory machines like the AI Max+ and DGX Spark became common, and people found they "fit the model but run slowly" (slow prefill). Using a cheap discrete GPU to speed up prefill is a real pain point, with lots of 395 vs 3060 comparison posts on Reddit and Medium.
- The content is well made: bilingual README, a 12-minute explainer video, many measured tables with CSVs, frequent version and changelog updates (252 commits). It looks like a serious lab.
- The stars are mostly bought: strong evidence of a fork bot pool, a steady-drip curve, and zero discussion off-platform. The high star count is itself the growth tactic, used to drive traffic to the commercial site and look credible in aggregators and GitHub search.
5. Differentiation
- Compared with exo and others: it doesn't build general-purpose software. It does measured tests and patches for "mixed consumer hardware," from a Chinese-community angle (domestic-only cards like the 6000D, used 3060/3080).
- The differentiation has some content value, but it is not why it got 1100 stars. Exo's blog posts and Reddit threads on the same topic get far more traffic. This repo has gone undiscussed off-platform, and the stars come mainly from bots.
6. Visibility and copycats
- Visibility: few people know about it yet. Only automatic aggregators index it off-platform; zero mentions on X, Reddit, or HN. No media, no big-account reposts.
- Copycats: no repo found that directly copies it. The established project on the same topic (exo) came earlier.
7. Takeaways
- The "public measured data + explainer video + private key patches" open-source front door can turn a hardcore topic into an entry point for renting machines, selling tokens, and recruiting into groups.
- Getting Chinese-language "how to build it" content out ahead of the hardware cycle (395, Spark, 6000D) has real search demand.
- Cautionary lesson: bought stars won't get a repo onto trending, and they don't create off-platform discussion. Real conversions are probably only single-digit issues.
8. Still unclear
- Star accounts can't be checked directly (the stargazers endpoint returns empty for our token). The bot judgment rests on the fork-account pool plus the curve shape, which is a strong inference.
- Whether the Bilibili "AI观模者" video mentions this repo has not been verified.
- The actual rental volume and revenue on qlsoulmate.com are not visible (the leaderboards on the page still show "loading" or "coming soon").
- Whether the benchmark data itself is reproducible has not been verified.