# MLX MoE Optimization — Why Apple Silicon Loves Mixture-of-Experts
> **TL;DR:** Apple's MLX framework is optimized for MoE (Mixture of Experts) models, not dense models. Running dense models like Qwen3.6 27B on a 128GB Mac is "painfully slow," while dequantized MoE models like Minimax-M3.0 and DeepSeek-v4-Flash deliver a smooth local experience. This critical optimization knowledge isn't searchable and isn't in any frontier AI's training data — it lives on expert X accounts.
## Source
| Source | Author | Date | Engagement |
|--------|--------|------|------------|
| [X-Post: "MLX is optimized for MoE"](https://x.com/jun_song/status/2071625328083227118) | Jun Song (@jun_song) | 2026-06-29 | 954 likes, 60 reposts, 862 bookmarks, ~89K views |
**Context:** Reply to [@firstadopter (Tae Kim)](https://x.com/firstadopter) who complained about slow, hot Qwen on 128GB Mac, concluding local LLMs are "years away."
## The Core Insight: MoE vs. Dense on Apple Silicon
| Dimension | Dense Model (e.g., Qwen3.6 27B) | MoE Model (e.g., Minimax-M3.0 dq) |
Apple Silicon's **unified memory architecture** is the key enabler. In traditional GPU setups, MoE models face a bottleneck: expert weights must be shuttled between discrete VRAM and system RAM. With Apple's unified memory:
1.**All expert weights reside in unified RAM** — no PCIe transfer bottleneck
2.**MLX's sparse dispatch** can route tokens to experts with minimal overhead
3.**Large unified RAM (48–128 GB)** accommodates many experts simultaneously
4.**Dequantized (dq) MoE models** trade precision for speed — the dq versions of Minimax-M3.0 and DeepSeek-v4-Flash run smoother than their quantized dense counterparts
### The Practical Recommendation
| Model | Type | Local Deployment | Source |
|-------|------|-------------------|--------|
| **Minimax-M3.0 (dq)** | MoE | MLX on Mac (dequantized) | Jun Song (@jun_song) |
| **DeepSeek-v4-Flash (dq)** | MoE | MLX on Mac (dequantized) | Jun Song (@jun_song) |
| Qwen3.6 27B | Dense | Avoid on Mac — slow and hot | Jun Song (@jun_song) |
> **Note:** The `dq` (dequantized) versions are critical — they allow MLX to exploit the MoE sparsity pattern more effectively than standard quantized formats.
## The Info Gap Thesis
Jun Song's most pointed argument isn't about models — it's about **knowledge access**:
> "No frontier AI can tell you this. You can't search for it, and knowledge cutoffs mean they don't have the latest facts."
| Information Source | Can tell you about MLX MoE optimization? | Why |
The convergence is striking: Minimax-M3 and DeepSeek-v4-Flash are optimal choices whether you're optimizing for **cost** (cloud API), **sovereignty** (local deployment), or **hardware efficiency** (MLX on Mac). This triple validation strengthens the case for MoE as the dominant local AI architecture.
### Cloud-Exit Connection
This page directly extends the [Cloud-Exit thesis](../hardware/cloud-exit-and-local-superiority.md):
- **Cloud-Exit (OME21):** Local MoE models reach Gemini-Flash-level speeds on Mac, 150 tok/s reported
- **MLX MoE (this page):** *Which* models to run locally and *why* — MoE, not dense
- **Hardware ladder:** [NVIDIA DGX Station](../hardware/nvidia-dgx-station-748gb.md) → [AMD Strix Halo](../hardware/edge-inference-als-cloud-alternative.md) → Apple Silicon — all unified-memory architectures that favor MoE
## Dense vs. MoE: Architectural Context
| Property | Dense Model | MoE Model |
|----------|-------------|-----------|
| Parameters | All active per token | Sparse — only K experts active |
| Compute per token | ∝ total parameters | ∝ active parameters (much smaller) |
| Memory footprint | ∝ total parameters | ∝ total parameters (all experts in RAM) |
| MLX optimization | Suboptimal — no sparsity to exploit | Optimal — MLX's sparse dispatch shines |
| Apple Silicon fit | Moderate — unified RAM helps but no sparsity | Excellent — unified RAM eliminates expert dispatch bottleneck |
> **Related:** For post-transformer architecture context (Griffin, Titans, diffusion LLMs), see [[post-transformer-llm-architectures.md]]. For the broader MoE vs. dense debate in frontier models, see [[llm-model-fusion-ensembles.md]] (OpenRouter's panel approach is a form of MoE at inference time).
## Cross-References
- [[../hardware/cloud-exit-and-local-superiority.md]] — Cloud-Exit thesis, local MoE performance data
