Skip to content
Main Site News Console

Four major open weights dropped in 72 hours, and the only one that fits in 24GB VRAM is surprisingly from NVIDIA.

· Reddit · r/LocalLLaMA Translated
Reddit

What a week. Here’s a quick recap, with all figures sourced directly from official repositories and Model Cards:

Thursday: Meta released Muse Spark Open. 816B total parameters, 42B active, and a 1M context window. The announcement claims it brings agentic AI “to your desktop.” As it turns out, “desktop” here means a pair of 512GB VRAM M5 Ultra Mac Studios—a configuration Apple says won’t ship until “late October,” with pricing still TBA. Alternatively, you could run four 256GB Studios for around $38k. On top of that, it comes with a custom license: mandatory “Built with Muse Spark Open” attribution, plus a requirement to negotiate a separate commercial agreement once your revenue crosses $20M. Meanwhile, Meta’s own Model Card shows an Artificial Analysis Index score of 39, lagging behind GLM 5.3 (45) and Kimi K3 (44).

Same day: NVIDIA launched Nemotron 3.5 Bolt. 74B total parameters, 9B active, trained with quantization-aware training down to 2-bit, shrinking the entire model to just 22GB plus a 1.7GB vision projector. Purpose-built to squeeze into 24GB of VRAM. Day-one Unsloth GGUFs are available, with out-of-the-box support for llama.cpp, Ollama, and LM Studio.

Friday: Reflection finally made Beam official. 501B total parameters, 23B active, released under a clean Apache 2.0 license with zero strings attached. The smallest official checkpoint is NVFP4, weighing in at 294GB.

Saturday afternoon: DeepSeek casually dropped V4.1 Flash 1017 on X like it was just another routine post. Licensed under MIT. Their own benchmark tables show a score of 77.0 on DeepSWE compared to Opus 5’s 74.0 (vendor benchmarks, take with a grain of salt). The entire repository clocks in at 510GB.

So I put them all into a chart, plotted against the 24GB VRAM red line that most of us are holding onto.

A few takeaways:

  • “Running locally” has now officially morphed into “running on a rig that costs more than a car.”
  • The company that keeps selling us 24GB cards was, ironically, the only one this week to build a model specifically tailored for 24GB VRAM. Not sure if that’s benevolence or just another sales funnel.
  • Licenses mattered far more than parameter counts this week. DeepSeek and Reflection shipped under MIT and Apache 2.0, while the company shouting “open source” the loudest in their marketing slapped on mandatory attribution and commercial kickback clauses.
  • Mistral says weights for Large 4 (codename “Le Chonk”, 1T total parameters) will drop before the end of the month, so the 24GB club is about to feel even lonelier.

Top Discussions

Writer_IT (⬆56): It’s disappointing, sure, but new small and mid-sized models will definitely come along eventually. It’s only been a few months since Qwen 3.8 27b dropped for lower-VRAM GPUs, not to mention the absolute beast that is deepseekv4 flash vision within the realm of practical local inference. Honestly, I haven’t found anything it can’t handle, coding included. The progress made in just a single year is mind-blowing. Megamodels are still great for the ecosystem—they force cloud providers to slash their prices.

KontoOficjalneMR (⬆42): Plus, it’s a custom license: mandatory “Built with Muse Spark Open” attribution, and you have to negotiate a separate deal if you make over $20M in revenue. Meta’s own model card also ranks it at 39 on the Artificial Analysis Index, trailing GLM 5.3 (45) and Kimi K3 (44).

Moarkush (⬆158): “Open weights” has never meant “runs on consumer hardware.” Open weights just means it isn’t a closed, proprietary black box—it doesn’t mean “you can run it on a gaming GPU.”

theone_2099 (⬆39): Friendly reminder that “open weights” and “open source” are two completely different things.

615wonky (⬆87): You guys are sleeping on LFM2.5-24B-A2B, and you really shouldn’t be. It hits way above its weight class. https://huggingface.co/LiquidAI/LFM2.5-24B-A2B I asked it to write a radix-2 FFT in Python, and it nailed it on the first try. For this parameter class, its coding capabilities are seriously solid.

djc0 (⬆33): By the way, does anyone actually say “hits far harder than it has any right to” in real life? Or have we already started mimicking our AI overlords?

Acceptable_Push_2099 (⬆42): It has fewer active parameters, fewer total parameters, a smaller KV cache, and you think it’s more overrated than what was recently the best model at that MoE size?

mitchins-au (⬆34): Looking at their track record with ROCm support—especially for Strix Halo—it’s not hard to see why they didn’t bother.