Mac Studio M4 Max · 128 GB · local benchmarks

Index of published work

Every dashboard, report and demo on this site, grouped by line of work. Each card says what the page shows and when it was last updated.

Qwen3.8-Flash-Next — daily driver

Campaigns bench/qwen38-flashnext-daily-driver-2026-09 and bench/engine-updates-2026-10: quant × runtime combinations of Flash-Next (MoE), to pick the most responsive setup. Verdict from 2026-10-07: ddalcu iQ-MLX 4.7 bpw on mlx-serve 26.10.1. Daily driver since 2026-10-11: Swift 1.5 on the same runtime.

The best way to run Flash-Next on an M4 Max 128 GB

Public summary for readers outside this repo: five servers from 8K to 1M, agent turn time, prompt cache reuse, memory, a quality check and the commands. mlx-serve: 8.8 s per agent turn at 128K and 13.0 s at 512K. Splash 1.4.0 with Swift 1.5: 6.7 s at 512K and 9.3 s at 1M, but a change halfway re-prefills the whole prompt.

2026-10-26qwen38-flashnext-m4max-guide.html
How many agent sessions fit on one Flash-Next server?

Public summary for readers outside this repo: what happens to speed and waiting time when two, three or four agent sessions share one local server, and how to set up the launcher for it. 2 sessions is the maximum; each runs about 2× slower; running two together saves no total time.

2026-10-18qwen38-flashnext-concurrency.html
Campaign dashboard, October 2026

Four runtimes: headline numbers, bars per metric, gates per band, test coverage, a cheap quality check (HumanEval, tool calls) and the September uncensored stage. n2 wins with T_turn 8.23 s at 32K and 8.84 s at 128K.

2026-10-10qwen38-flashnext-overview.html
Five runtimes from 8K to 1M

October 2026 stack: mlx-serve 26.10.1 and 26.10.3, oMLX 0.7.0, MTPLX 2.12.2, ds4 and Splash 1.4.0. Lines per context for T_turn, warm TTFT, cold TTFT, decode, prefill and wired memory. Splash has the lowest T_turn in every band and is the only runtime at 1M; mlx-serve leads the four runtimes of the engine round; MTPLX refuses 256K (planned fit 237,568 tokens).

2026-10-26qwen38-flashnext-perf-lines.html
Where the thinking-effort line goes

The effort line first or last in the prompt, on Swift 1.5 and iQ-MLX: effort switch at 128K, prefix reuse on short prompts, obedience per level, time and tokens per question. Last: the switch drops from 167 s to 0.8–5.8 s and accuracy holds, but short prompts lose the shared prefix (53/55 → 0/55 reused).

2026-10-17qwen38-flashnext-effort-tail.html
Swift 1.5 vs iQ-MLX

Two 4.7-bit MLX packs of Qwen3.8-Flash-Next on mlx-serve 26.10.1: time per question as dot plots, tokens and generation speed, accuracy on six suites. Same accuracy; with the recommended sampling, 2–3× less time to the final answer on GPQA and LiveCodeBench, because Swift 1.5 thinks with fewer tokens.

2026-10-11qwen38-flashnext-swift15.html
Responsive driver — scoreboard

The campaign's first dashboard: verdict in prose, scoreboard per band, T_turn and TTFT lines, cache hit per scenario, wired memory and the 512K probe.

2026-09-14qwen38-flashnext-driver.html

Qwen3.8-27B — prefix cache, MTP and runtime

The dense 27B campaign: selection of runtime, quant, prefix cache and speculation. The September pages are kept as they were and are not maintained.

Local benchmarks

Speed and quality of local models measured on this rig, compared with frontier models.

Harnesses and agents

What local and frontier models produce inside coding harnesses from the same prompt: SVG drawings, a game and landing pages. Also field performance from day-to-day opencode use.

Demos

The builds the agents delivered, published as they are. They run in the browser.

No work matches the filter.