42B Active, 816B to Load: Why It Still Needs Two Macs
Meta Superintelligence Labs released Muse Spark Open, an open-weight model, on 2026-10-15: 816B total parameters with roughly 42B active per token in a sparse mixture of experts, natively taking text, image, video and audio input, a 1M-token context window, sharing the same base model as Muse Spark 1.3, and shipped under the Muse Model License, which Meta describes as "limited commercial terms, which allow many developers to use the model for free" - the LICENSE text governs and this article does not interpret its clauses. The point is not that another large model went open; it is the arithmetic that tends to get skipped. Activating 42B cuts compute per token, not the memory floor: the full checkpoint must stay resident, plus KV cache, activations and runtime overhead. A rough byte-level estimate (this site's arithmetic, not official data) puts BF16 at about 1.6TB, FP8 at about 816GB and 4-bit at about 408GB. That is why the official desktop recipe is two Apple M5 Ultra Mac Studios: 512GB of unified memory per machine, about 1TB combined, 1.2TB/s of bandwidth, running the latest Apple MLX, with Meta describing the pair as behaving like one supercomputer with a terabyte of unified memory. On the ecosystem side, seven inference runtimes support it at launch - SGLang, vLLM, TensorRT-LLM, Hugging Face Transformers, MLX, llama.cpp and Unsloth - verified on NVIDIA, AMD, Intel and Apple silicon, with four quantization branches (BF16 and NVFP4 from Meta, FP8 and MXFP4 from AMD, INT4 and MXFP4 tuned for Intel Crescent Island, GGUF from Unsloth), speculative-decoding drafts from SGLang's DFlash V2 and vLLM's DSpark, and PyTorch-native Helion kernels inside SGLang that Meta measures at 1.03x to 3.95x at kernel level plus a 3 percent end-to-end gain on AMD MI350, all vendor-measured. On safety, this release adds post-training relative to the August Muse Spark, evaluated under Meta's Superintelligence Scaling Framework to its release threshold, with the full evaluation report described as coming soon. Three gaps must be stated plainly: Meta has not published the precision, actual memory footprint or usable context of the desktop demo; it has given no inter-machine bandwidth or latency; and it has given no tokens per second. According to dev.to citing Meta's own comparison chart, a second-hand account and not an independent reproduction, the model places first in six comparisons including the tool-use benchmarks JobBench and MCP-Atlas, yet trails Kimi K3 and GLM 5.3 on GDPVal-AA, which covers terminal coding and long-horizon software engineering. Division of labour with this site's 2026-07-31 piece on Muse Spark 1.1: that article covered the closed 1.1 and Meta's first paid API, while this one covers the open-weight release and how it actually runs.