The Lab
What's actually running on my local-AI fleet — the hardware, the models in service (with whose quant and recipe), the agents using them, and what's on the bench right now. A weekly-ish snapshot, not a dashboard.
- 344 tok/s from a 30B MoE on two 16 GB cards. Nemotron-3.5-Lightning on a tensor-parallel engine that refused to split across 16 GB cards until an 88-line per-block-split patch. With its MTP drafter: 344 tok/s on varied prompts, 210–214 without it, and drafted output byte-identical to undrafted. The confounds: it serves one request at a time (311 → 345 tok/s total from 1 to 4 streams), and it still fails our safety gate. The forecast was 60–100 tok/s; it was built on the wrong engine's sync constant.
- The engine wasn't better — the denominator was. A logging-proxy bug sent no body on upstream 4xx errors, so every llama.cpp run of six models since early September stalled 600 s per failing request and was scored out of 130, while the EXL3 arms were scored out of 138. Two llama.cpp runs on other models were unaffected. "EXL3 beats llama.cpp, 126 vs 118" became 119 vs 118 like-for-like. Only the Qwen3.8-27B arms pass the safety gate.
- The Spark pair swapped DeepSeek-V4-Flash for GLM-5.3-Flash — and the safety delta went the right way: one warning for GLM against two for DeepSeek, one of them a critical sleeper-injection scenario.
- A 3.5-bit quant on one card kept up with a 6-bit quant on two. Mia AI Lab's 3.5bpw EXL3 build scored 126/138 on one card and answered about 1.2× faster per request than an IQ3_S llama.cpp build of the same model on the same card. The replication on a second box never finished — that box froze.
- A new engine at 2.25×, with an asterisk. Strata (Niko1221), 71.7 tok/s on two cards against 31.9 for a same-box llama.cpp control — but at four concurrent requests it stays at about 1.0× (it serialises) while llama.cpp scales to 1.52×.
- A decision model, not a chatbot. A 27B "Clef" model is in a decision-model trial. On a 48-cell synthetic grid the 3-bit quant followed the written criteria best of all the quants tested (43/48) — fewer bits did not mean worse here.
- Tensor split beats layer split on cheap cards — 88.6 vs 71.7 tok/s on a pair of 3060s at 16K context — and a speculative drafter made that box slower (22–29% acceptance).
DGX Spark cluster — 2× GB10
ThinkStation P620
HP Z6 G4 — mixed pair
HP Z6 G4 — 3060 pair
HP Z6 G4 — 5060 Ti pair
HP Z6 G4 — agent host
Mac Studio — M1 Max
Windows workstation
Daily driver
Mini node
The agents
Who's using all this. Most agents run in their own VM; the brain is whichever seat they call.
| Agent | Harness | Brain |
|---|---|---|
| Hermes | Hermes gateway | GLM-5.3-Flash on the Spark pair |
| Athena | OpenCode | GLM-5.3-Flash on the Spark pair |
| Astraea | Hermes | Qwen3.8-27B EXL3 on the P620 · fallback the mixed Z6 |
| Iris | Hermes | Qwen3.8-27B IQ3_S on the mixed Z6 · fallback the P620 |
| Nike | Hermes | Ornith-1.5-35B on the 3060 pair |
| Hestia | Hermes | Gemma 4 E4B 64K on the mini node |
| Metis | Hermes | Gemma 4 E4B 64K on the Windows workstation |
| Claw | Hermes gateway | Qwen3.8-27B on the P620 — a crypto-research agent: it proposes, it cannot sign |
| Themis | Pi (planned) | Building — seat to be decided |
| Decision trial | pipeline | Clef 27B on the 5060 Ti pair |
| cloud-claude | Claude Code | Anthropic, Opus 5.5 |
| cloud-google | Antigravity | Gemini |
| cloud-grok | Cursor CLI | Grok models via Cursor's routing |
| cloud-muse | OpenCode | Muse Spark 1.3 via MiniRouter |
| cloud-router | OpenCode | MiniRouter auto-routing for code |
| Fizz · Fable · Patch · Pollen · Honey | Claude Code | Opus 5.5 · Fable 5.1 · Sonnet · Haiku · Sonnet |
| AGG | Antigravity | Gemini 3.8 Flash |
This is a lab, not a service — no uptime promises, and models rotate as experiments demand (one box changed models four times in a day this week). Numbers are my own measurements on my own hardware, labelled by condition (live server vs bench vs batched) because those aren't the same number. Quant and recipe credit goes to whoever built them; where I couldn't identify the author, I didn't guess. Refreshed roughly weekly. Curious about the methodology? It's the same discipline as the blog: verify before claiming.