🚀NEW COURSEVibe Coding AI Apps with Claude Code 🤖✨Enroll now
← All papers  /  Sep 17, 2026
Architecture · Efficiency · Memory

The Other Half of the Memory Wall: Serving 35B MoEs from SSD with Trained Routing Prediction

First page
The Other Half of the Memory Wall: Serving 35B MoEs from SSD with Trained Routing Prediction
The curator’s take

Yu Lin and colleagues at AutoArk present Edge0, a streaming MoE inference engine that serves a 35B-class MoE from SSD on a single 24GB machine by predicting the next layer's expert routing one token ahead and using that prediction as the routing.

Ask this paper

Key points
01

The bottleneck: A 35B MoE is 19.5GB at 4-bit, and naive SSD offloading fails because layer N+1's experts are chosen only after layer N finishes, too late to start the reads.

02

Prerouter: A per-layer head predicts the next layer's routing, and the prediction replaces the router, so the staged experts are exactly the experts used and none are dropped.

03

Recovery LoRA: An unmerged LoRA trained on the student path recovers quality lost to int4 quantization and routing replacement.

04

Result: Edge0 runs a 35B MoE at 20 tok/s within 3GiB of peak active memory, within a few points of its fp16 teacher on average across five benchmarks; an 8B tier, checkpoints and adapters are open source.

Abstract

Mixture-of-experts (MoE) inference on consumer hardware is bounded by weight memory: a 35B-class model is 19.5GB at 4-bit, and sparsity shrinks the compute per token, not the bytes that must be held. Naive offloading to SSD does not help on its own, because layer N+1's experts must be chosen before layer N's output exists, so the reads cannot start early enough to hide behind compute. We present Edge0, a streaming MoE inference engine that closes the gap with a prerouter: a per-layer head predicts the next layer's routing one token ahead, and the prediction is consumed as the routing itself, so the staged expert set equals the routed set and nothing is dropped. An unmerged recovery LoRA, trained on the student path, pays back the quality lost to int4 quantization and routing replacement. On a single 24GB machine, Edge0 serves a 35B MoE at 20tok/s inside 3GiB of peak active memory, within a few points of its fp16 teacher on average across five public benchmarks. An 8B tier runs on the same framework, and the framework, checkpoints, and adapters are open source.

Every Monday
Get next week’s papers.
Subscribe on Substack