Apple clusterThunderboltexpert

What runs on 4× Mac Mini M4 Pro Exo cluster (256 GB total)?

Four Mac Mini M4 Pro nodes with 64 GB unified memory each, connected via Thunderbolt 5. Exo distributes layers across machines. 256 GB total / ~180 GB effective for inference.

At a glance
Effective VRAM
180 / 256 GB
Not pooled
Speed penalty
~60%
vs ideal single-card
Recommended runtime
exo
pipeline parallel
Setup difficulty
expert
~600W peak
24
Models fit
6
Borderline
8
Not practical
Deployment recipe
Multi-machine Apple cluster

Exo-based multi-Mac sharding over Thunderbolt 5 — the cluster recipe for >192GB unified memory targets.

Memory budget
Total VRAM
256 GB
Effective for inference
180 GB
70% of total
Not pooled

Exo clusters 4 Macs into a single inference target by sharding model layers across machines. Total memory is 4× 64 = 256 GB, but each node reserves OS overhead and KV-cache buffers, and inter-node communication costs ~10-15% effective capacity. Concretely: a 200B-class model at Q4 (~110 GB) distributes across 4 nodes with ~25-30 GB per node, leaving comfortable headroom on each. Thunderbolt 5 (80 Gbps bidirectional, 120 Gbps in display mode) is the communication path — meaningfully faster than 10 GbE but ~10× slower than NVLink. Layer-split via Exo is the only practical strategy; tensor parallelism over Thunderbolt is too latency-bound to be useful.

Why total VRAM is not the whole story

Distributed across multiple Macs over Thunderbolt. Each node runs Exo's layer shard — total 256 GB of memory but inter-node latency caps single-stream speed. Effective ~180 GB after cluster overhead.

See the multi-GPU guide for topology tradeoffs, and the RunLocalAI Will-It-Run Framework for the citable fit-tier method.

Topology

Topology
apple-cluster
Interconnect
thunderbolt~80 GB/s
Component count
4 units
Components
Recommended runtime
exo
Also: mlx-lm
Recommended split strategy
pipeline-parallel
Also: layer-split
Setup difficulty
expert
~600W peak

Models that fit comfortably (24)

Effective VRAM utilization ≤ 85% at the smallest production quant. Comfortable headroom for KV cache.

200B·AWQ-INT4140 GB·78% of effective VRAM·~60% speed penalty vs ideal
GLM-5
Fits
200B·Q4_K_M140 GB·78% of effective VRAM·~60% speed penalty vs ideal
144B·AWQ-INT496 GB·53% of effective VRAM·~60% speed penalty vs ideal
141B·Q4_K_M96 GB·53% of effective VRAM·~60% speed penalty vs ideal
141B·Q4_K_M96 GB·53% of effective VRAM·~60% speed penalty vs ideal
132B·AWQ-INT496 GB·53% of effective VRAM·~60% speed penalty vs ideal
132B·Q4_K_M96 GB·53% of effective VRAM·~60% speed penalty vs ideal
123B·Q4_K_M88 GB·49% of effective VRAM·~60% speed penalty vs ideal
120B·Q4_K_M84 GB·47% of effective VRAM·~60% speed penalty vs ideal
109B·Q4_K_M80 GB·44% of effective VRAM·~60% speed penalty vs ideal
105B·Q4_K_M74 GB·41% of effective VRAM·~60% speed penalty vs ideal
105B·Q4_K_M74 GB·41% of effective VRAM·~60% speed penalty vs ideal
104B·Q4_K_M70 GB·39% of effective VRAM·~60% speed penalty vs ideal
104B·AWQ-INT472 GB·40% of effective VRAM·~60% speed penalty vs ideal
90B·Q4_K_M60 GB·33% of effective VRAM·~60% speed penalty vs ideal
90B·AWQ-INT464 GB·36% of effective VRAM·~60% speed penalty vs ideal
78B·Q4_K_M52 GB·29% of effective VRAM·~60% speed penalty vs ideal
72B·Q4_K_M48 GB·27% of effective VRAM·~60% speed penalty vs ideal
72B·Q4_K_M48 GB·27% of effective VRAM·~60% speed penalty vs ideal
72B·Q4_K_M48 GB·27% of effective VRAM·~60% speed penalty vs ideal
72B·AWQ-INT448 GB·27% of effective VRAM·~60% speed penalty vs ideal
70B·Q4_K_M48 GB·27% of effective VRAM·~60% speed penalty vs ideal
70B·AWQ-INT448 GB·27% of effective VRAM·~60% speed penalty vs ideal
70B·Q4_K_M48 GB·27% of effective VRAM·~60% speed penalty vs ideal

Borderline (6)

Fits but with little headroom. KV cache for long context may not fit; verify before deployment.

284B·Q4_K_M192 GB·107% of effective VRAM·~60% speed penalty vs ideal

Effective VRAM utilization >107% — KV cache for long context will not fit. Cap context at ~4-8K or move to a larger combo.

253B·Q4_K_M160 GB·89% of effective VRAM·~60% speed penalty vs ideal

Combination fits but with little headroom. Verify KV cache budget for your target context window before committing.

236B·Q4_K_M160 GB·89% of effective VRAM·~60% speed penalty vs ideal

Combination fits but with little headroom. Verify KV cache budget for your target context window before committing.

236B·Q4_K_M166 GB·92% of effective VRAM·~60% speed penalty vs ideal

Effective VRAM utilization >92% — KV cache for long context will not fit. Cap context at ~4-8K or move to a larger combo.

236B·Q4_K_M160 GB·89% of effective VRAM·~60% speed penalty vs ideal

Combination fits but with little headroom. Verify KV cache budget for your target context window before committing.

235B·Q4_K_M160 GB·89% of effective VRAM·~60% speed penalty vs ideal

Combination fits but with little headroom. Verify KV cache budget for your target context window before committing.

Not practical (8)

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly. Drop to a smaller quant or move to a larger combo.

1600B·Q4_K_M1024 GB·569% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

Step-3
Not practical
1000B·AWQ-INT4640 GB·356% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

Kimi K2.6
Not practical
1000B·Q4_K_M700 GB·389% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

DeepSeek V4
Not practical
745B·AWQ-INT4480 GB·267% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

675B·Q4_K_M448 GB·249% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

671B·Q4_K_M420 GB·233% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

671B·Q4_K_M420 GB·233% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

Llama 4 405B
Not practical
405B·AWQ-INT4280 GB·156% of effective VRAM·~60% speed penalty vs ideal

Model weights exceed effective combo VRAM. Even with the recommended split strategy, this configuration won't run cleanly.

Benchmark opportunities

estimates, not measurements

Pending benchmark targets for this combo. Once measured, results land in the catalog as benchmarks.

4× Mac Mini M4 Pro Exo cluster + Llama 3.1 70B (MLX-4bit)
pending
Estimate: 4-9 tok/s decode (Thunderbolt 5 inter-node)

Multi-Mac Exo cluster. 70B at MLX-4bit (~40GB) shards across 4 nodes; Thunderbolt 5 latency dominates. Compare against single Mac Studio M3 Ultra to quantify cluster overhead.

Going deeper