Papers

DeepInfer-Mac 在 24 GB MacBook Air 上跑 750B 级 DeepSeek-V4.1-Flash

DeepInfer-Mac: Running a 750B-Class MoE on a 24 GB Laptop

Why we picked it

斯坦福之外也有人把 750B 的 DeepSeek-V4.1-Flash 塞进了 24 GB 的 MacBook Air,速度只有 0.21-0.72 tokens/s,但论文把权重加载和预取设计讲得很透,做本地推理的值得看实现细节。

DeepInfer-Mac 把 750B 级的 DeepSeek-V4.1-Flash 放进只有 24 GB 统一内存的 MacBook Air 运行。模型经混合低比特转换后占 338 GiB SSD 空间,常驻权重仅约 7.6 GiB,路由专家和 Engram 行按需加载。端到端测试中生成英文、中文和代码的速度为 0.21-0.72 tokens/秒,采样进程最大内存占用 16.73 GiB。对比实验显示,下一层预取在常驻专家重叠之上再带来 21.0% 的吞吐提升。

Original · arXiv: DeepSeek

DeepInfer-Mac: Running a 750B-Class MoE on a 24 GB Laptop

DeepInfer-Mac runs the 750B-class DeepSeek-V4.1-Flash model on a MacBook Air with 24 GB of unified memory. A mixed low-bit conversion occupies 338 GiB on the internal SSD. About 7.6 GiB of weights remain resident; routed experts and Engram rows are loaded when needed. This separation makes the model executable, but it leaves each generated token waiting for a succession of storage reads. We organize expert weights so that reads fill reusable GPU buffers directly, and couple cache allocation with the lifetime of those buffers. In end-to-end runs, the system generates English, Chinese and code at 0.21-0.72 tokens per second, with a largest sampled process footprint of 16.73 GiB across the tested requests. Matched decode comparisons show a 21.0% throughput gain from next-layer prefetching over resident-expert overlap alone, at the cost of additional reads. Longer prompts remain costly. We describe the design, provide the implementation and measurement scripts, and identify the limits of this operating point: a model far larger than memory can run locally, while storage and prefill still govern the user's wait.