Live data from Hacker News

Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

research.meta.ai

11–20 of 675 posts

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#11
Wow, Meta is back (at least for now)!

I like this class of model. Multi-token prediction makes it viable to run dense models at not-too-far-off speeds as MoE models with much better intelligence.

The submission’s title (open weights 30B local coding model) is luckily wrong: This is meant to be a general agentic model.

It even comes pre-quantized and with a MTP/drafter model. Looking good!

Let’s hope they aren’t dishonest with the benchmarks this time …

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#12

What I think would be perfect is a model that could run on a single DGX spark and be competitive with DSV4 Flash 731. Flash is already a game changer. Hopefully meta plans on this, like the old 70b. V4 flash is smart enough for any use but slightly too big. 27b-30b isn’t intelligent enough.

DSV4 Flash 0731 already runs on RTX 4090 24GB + 128GB system RAM at a usable tok/s and quantization.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#14
The more open weight models get released the greater the market for personal and small business oriented hardware to run these models. This will drive lower cost hardware, which has stagnated in recent years due to most software not needing the performance and capacity.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#15

Still needs 32-64GB memory to run it locally. 64GB Macbook pro with an M5 chip costs more than 4k Euros in Germany. A more practical model would be a language specific (e.g Python or JVM language) and excellent at tool calling and reasoning. Maybe that way they can shrink it even more.

There have been discussions on language specific not really being a relevant change to reduce size.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#16

Still needs 32-64GB memory to run it locally. 64GB Macbook pro with an M5 chip costs more than 4k Euros in Germany. A more practical model would be a language specific (e.g Python or JVM language) and excellent at tool calling and reasoning. Maybe that way they can shrink it even more.

I feel like we’ve had this discussion before. From what I remember, specialized models rarely do that much better than general ones, hence no mode Codex models.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#18

Still needs 32-64GB memory to run it locally. 64GB Macbook pro with an M5 chip costs more than 4k Euros in Germany. A more practical model would be a language specific (e.g Python or JVM language) and excellent at tool calling and reasoning. Maybe that way they can shrink it even more.

Even if you had a 64GB machine: Are you willing to reserve 90% of your memory to run a LLM? With dirt cheap models like deepseek-v4-flash that will run "forever" on $10, the answer for me is clearly: no.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#19
post #12

What I think would be perfect is a model that could run on a single DGX spark and be competitive with DSV4 Flash 731. Flash is already a game changer. Hopefully meta plans on this, like the old 70b. V4 flash is smart enough for any use but slightly too big. 27b-30b isn’t intelligent enough.

DSV4 Flash 0731 already runs on RTX 4090 24GB + 128GB system RAM at a usable tok/s and quantization.

You personally? Just curious. Context window is also a factor and ram isn’t really cheap. Sparks are assembled units which I like.
Post reply on HN