The memory trade-off
There is no combined unified-memory pool. Each Mac keeps its own memory, and the model is divided across the pair. Sharding lets the pair run a model that exceeds one Mac’s capacity. Each rank still needs space for its shard, KV cache, and runtime overhead. Measure GPU-wired residency with the platform’s wired-memory accounting, not a process’s RSS. Unified-memory allocations may not appear in a process’s RSS.Two workers or one sharded model?
- If it fits on one Mac, run an independent worker on each and divide requests between them.
- If it does not fit, shard one model across the pair. This trades link traffic and coordination for additional model capacity.
Historical benchmark snapshot
A prior measurement snapshot recorded the then-selected model at the following concurrency levels:
Those figures are historical results for the model and configuration used then. The current model selection and benchmark results are UNKNOWN on this page.
Historical record
The prior automatic link watcher, retry, and recovery lifecycle was removed on 2026-10-18 in favour of manual join and detach. Older root-cause and incident details are historical and belong to the private operational reference.Related
Models and quantization
Model formats and quantization choices for local inference.
Apple Silicon stack
The single-Mac serving stack and its tuning controls.
Benchmarking
The method and result records for MLX benchmarks.