Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows
https://research.meta.ai/blog/introducing-muse-glimmer-open-agentic-modelEDIT: An open weight version of Muse Spark 1.2 is going to be released as well:
https://x.com/alexandr_wang/status/2086756152034066792
https://xcancel.com/alexandr_wang/status/2086756152034066792
But I have to say, I quite like the way Muse Glimmer thinks and talks. It's a cocky bastard in tone, but it's quite good, and its thinking traces are relatively terse.
Like, in the car wash test, this was in the thinking traces:
“Walking won't get the car washed.”
and:
“Perhaps answer: Walk if you want to wash yourself? No”
Which made me laugh out loud.
Even in the final answer:
- - -
You have to drive it. Walking 50m won't get the car clean, it'll just get you to the car wash.
If you mean you going to the car wash to check prices / pay / get a brush, then yeah, just walk the 50m. It's about 30 seconds on foot and you save the cold-start emissions of firing up the engine for a distance you could roll.
If you mean the car itself getting washed, the car needs to be at the car wash. You can push it 50m for a workout, but driving it 50m is the practical way.
- - -
The emphasis on "you" was from the model. I mean I write like this so I can't judge its tone harshly :-)
ETA: The knowledge cutoff is January this year, so it didn't encounter car wash discourse in the scraped training set, though I suppose you can't rule out some kind of fine tuning to deal with this scenario. Still made me chuckle.
ETA 2: obviously I wrote this before you added your last paragraph. WTF dude.
AI companies release models when they are ready - not on a set schedule. The steps are required to produce a release candidate, so a company can choose to bless the RC with the best metrics at any time - or alternatively continue (post/)training newer RCs if they feel they can do better, and they have time. When a model is ready for release is subjective, and can take into consideration what the competition is doing.
An obvious counter-example to schedules driving releases is the still unreleased Gemini 3.6 Pro.
The whole class of what can reasonably fit in a single GPU is an interesting category of LLM, and based on the results I've seen from 3.6 35B A3B and 27B versus what existed a year prior, it seems there's a lot of room for advancement.
</div> is four Gemma4 tokens, but one Qwen3.6 token.
Considering that Meta distills Qwen[1] (and should!), it'd be hilarious if Muse loses the head-to-head; the "distillation attack!!1!" people claimed distillation on release n-1 is enough to match the intelligence of the latest version.
1. They wrote a paper about it
Each turn is about 45-60 seconds to generate all of the various responses. The GM and director have reasoning on, and the NPCs/Location/Narrator do not.
It's a fairly good "engine" for that. I'm not sure how a denser Qwen would do here regarding speed.
Try a system prompt requiring it to think in Mandarin, while still delivering the response in the user’s language.
Huh, well... no? Gemma A4B and Qwen A3B are quite popular in fact. I'm sure 3.8 35B A3B will outperform 3.6 27B by all metrics
Qwen3.6 is a definitive, significant downgrade from Qwen3.5 for creative writing and prose for example. Yes, it's better at agentic and coding, but it regresses in many non-coding areas compared to Qwen3.5.
Of course, I do expect the 3.8 ones to perform better for agentic coding.
Tech tends to get boring when you judge current products against the hypothetical capabilities of unannounced products that may never ship. It's like comparing Nikon cameras against Canon camera rumours, or comparing iPhones against unannounced and therefore largely imaginary Samsungs.
- If they do a Qwen 3.8 35B A3B (and I hope they do because I love the 3.6 version)
- and if it beats 3.6 27B by all metrics
… then the local open weights world will be a better place.
But they have said nothing about it and they dropped several weight classes for 3.6, so who is to say they won't drop the 35B? And even if they don't, this is a tall order; why would the MoE tradeoffs no longer be apparent? (Again, I really like both the Qwen and Gemma MoEs)
FWIW I am enjoying testing Muse Glimmer — it's really quite impressive on chat, has nice terse and even amusing thinking traces, a bit of brass to it, and I'm hoping it will be good on agentic stuff.
Surprising that Meta don't host this model, even as rate-limited free-tier.
> open weight version of Muse Spark 1.2
Wait. Is this "version" different from what Meta serves?
UPD. was wrong on smaller, it's actually much larger
- muse glimmer: 15.9GB
- qwen 3.6 27B: 17.6GB
My video card is so close to its limit that these GB thresholds are mattering too much for me :D
Non-forking httpd servers using select() were a popular little coding challenge for a while in the 90s. Spinner was one of them.
Nginx’s real strength was being able to proxy and cache HTTP using that same mechanism, so you didn’t additionally need to deploy Varnish or some other appliance.
As to whether this is a good mental model for what is coming for local LLMs, I am not sure I am convinced. Apart from more quantisation-aware training, perhaps binary and ternary aware training, custom inference engines per model, and maybe some improvements in diffusion models, the grand challenge in small footprint LLMs is training really small reasoning and tool use models, and so far it’s far from clear they can deliver.
Truly tiny models will not be viable as general coding assistants; even 12B dense is too small and you will find plenty of people who will tell you that 26B/4B or 35B/3B MoE is too. Though perhaps they can be trained for single languages, like just Python or just TS/JS.
More likely is the idea that 30-40B dense models might be good enough for most things once low cost and likely bespoke hardware catches up.
But I don’t think any truly profound advances seem likely in software or training alone. I am no expert but it feels like we’re already a lot closer to efficiency than we were in your analogy, and the gains are perhaps not going to be much more than small increments.
Maybe we will see something like a ternary 60B/10B MoE model turn up. But at the moment at least I am not sure where the incentives are to train these.
My naïve impression is that the LLM world will keep delivering these fractional improvements for some years at the cost of simplicity. And sure, ontological support seems quite promising.
But making things radically better or faster for small models in the way that is hypothesised, that feels like it can only come as a result of hardware performance improvements and likely architecture changes.
Because there's no free lunch, right? Speculative drafting for example, noticeably improves performance until acceptance rates drop for reasons that have to do with the particular application, and then it starts hurting you, especially near the limits of the memory bandwidth. Because once it is wasteful it is an extra overhead.
I gather Gemma 4 supports, in principle, dynamic speculative draft lengths, to help with this — where it will stop making bold predictions when the success rate falls. But I'm not sure if any of the inference engines I've tested with support that.
I think small models are miraculous — I still think Gemma 4 12B is astonishing — but I guess what I am saying is that I think maybe technology is moving quickly enough that the developers are done with the low-hanging fruit.
Small llms are still way more efficiently server on big GPUs.
Sharing server capacity takes advantage of the massive parallel throughput and sharing of memory bandwidth.
You are sharing the GPUs with thousands of concurrent users.
Many analysts (and Microsoft) think even now that if everything committed gets built there will be considerable oversupply and there is not the revenue to pay for it.
If small models do continue to improve in unusual ways (I think there are limits) then the marginal need for cloud AI compute could fall precipitously beyond current estimates. The marginal need for consumer AI could almost totally collapse if someone makes good progress on very small reasoning and tool-calling models (which is a modestly big if)
The possibility of the data centre boom resembling the Chinese real estate bubble is not inconsiderable.
for clarity, I'm not agreeing with GP that small models will mean doom for data center projects
"... Soon we'll also release the weights for Muse Spark 1.2, our latest foundation model..."
This is bigger news - good for self hosting enthusiasts and a strategically sound move for Meta. Any push towards 'anti Chinese' models will directly benefit Meta as the competition on the frontier open-weights American models is almost non-existent. Meta will have no problem being #1.
Had Deepseek V4 Flash 0731 not launched, their latest Laguna release was really intelligent at non-coding tasks and it would have been my go-to model for my local workloads.
Starting this morning I am running their new local 30B model muse-glimmer on my old MacMini 32G using Ollama (remember to increase the context size!) and pi coding harness. I am getting good results with muse-glimmer running locally, with the caveat that everything runs slowly (e.g., give it a task and then go walk outside or do Qi Gong exercises for a while).
Things went from "local models are useless unless you have a 512GB GPU I guess" to "oh.. I can do a lot of stuff locally now!"
The quantized releases often change in the weeks following release as new improvements are discovered, so either use a tool that checks HuggingFace for new versions or manually check back in a few days or weeks to check for improved versions.
Initial reports are good. It hasn't been out long enough for anyone to really test thoroughly, but the people I know who have stable non-public test cases are reporting impressive results compared to even Qwen3.6 27B. That's a good sign that this might not be benchmaxxed (trained to excel at public benchmarks with less impressive performance on general tasks) which has been becoming common with recent releases.
www.reddit.com/r/localllama is a good place to keep up with the details from people who are actually using it. It feels strange to recommend a subreddit over Hacker News, but on this topic the /r/localllama threads are much more on topic right now if you're looking for information about the model.
There are some initial reports that even the 2-bit quantization is looking somewhat usable. That might make it small enough to squeeze into 16GB GPUs. I'd take those reports with a grain of salt because early tests are often optimistic and I've yet to see good results from anything 3-bit or less, but it should be fun to experiment with.
1. The template name is Onyx ATEM as found in the tool call exception message
2. It appears to be following a harmony-style chat template. But the tool use seems to be a xml like :<atem:function_calls> / <atem:invoke> / <atem:parameter>
3. atem: a internal joke of meta in reverse?
https://huggingface.co/meta-models/Muse-Glimmer-30B/blob/mai...
I think it’s likely 3; meta in reverse. While tokenisers and preprocessing can catch it, you want your special tokens to be unique and not present in the original corpus. <meta: is likely too common.
also perhaps taking some small joy from the lexical similarity to aten[0] namespace that lies at the heart of pytorch
[0]: https://github.com/pytorch/pytorch/blob/main/aten/src/README...
[1]: Limits may change without notice, including due to capacity constraints. - https://support.google.com/gemini/answer/16275805?sjid=14713....
[2]: "standard limits" are never defined - https://support.google.com/gemini/answer/16275805?sjid=14713...
[3]: https://tobyonfitnesstech.com/blog/anthropic-refund-scam/
Maybe in the very long term. If companies go local, the efficient model is to buy some big hardware to share among developers.
I run local models. Even with 128GB unified memory systems or a 5090 or RTX 6000, the generation speeds X model quality X context length is still far behind what I get from my SOTA model subscriptions. I also pay a lot more for the locally generated tokens in electricity and hardware costs. I'm also limited in parallel requests to the local box. The list goes on.
I really like running local models, but for any given point in time it's more efficient to have a big central box aggregating requests and churning through them. So maybe companies buy $300K servers and try to split it among 30 users instead of trying to buy 30 x $10K boxes.
More likely, they rent time on cloud servers by the month so they can adapt the hardware when new models come out with new requirements.
Then some day in the distant future when hardware is cheap and plentiful again, it might make sense for us to go back to individual boxes under the desk.
Surely, even if you’re just using open weights models, it should theoretically be cheaper to use them in a highly optimized cloud architecture(even with vendor markups) rather than each person serving their own models from much less efficient (and more importantly, much less consistent volume) self-owned “server under your desk”?
I haven't had to micromanage to this level. I usually start with a spec for a feature, which will be as detailed as I am opinionated about the feature. But it's usually on the level of a high-level context, plus some key implementation details (technology choices, key requirements, maybe an interface/API specification to 80% detail), and then the project already has high-level policies documented about e.g. how to structure files within the project.
Then I do a planning phase, task breakdown, and implementation of subtasks all within the model. I do read through it, but mostly the quality is good and I might make a couple notes. Then I do a review phase, which usually picks up a couple things. I'm moving towards less manual review of results and more automation as I learn what I can and can't trust the model with.
There's definitely a capability gap vs. larger models, but honestly I kind of prefer this workflow, as I stay more in touch with how the codebase is structured.
And it's great to be able to experiment as much as I want without worrying about how many tokens I'm burning or how close I am to a usage limit.
Looking forward to the 3.8 27B release to compare.
DS v4 Flash update maybe, but it is too big for typical Joe's desktop.
If you want to host the model on the server under your desk, you can. If you want to build a data center on-prem to host it, you can. If you want to pay a cloud provider to host it at their data center until you figure out how to scale it without their help, you can. It's like when people were first building commercial services to support Linux-based OSes, and people were also still hacking on it on local machines.
APIs may still have their place - maybe you just want to throw your devs a known quantity with all of the management built in - but it's not going to make Sam Altman a trillionaire, which is something anyone outside of the SV echo chamber could have figured out as soon as the first real competition to OpenAI emerged.
Until A100 prices are reliably under 1.70$ an hour, there is no GPU/AI bubble and Michael Burry doesn't know anything about GPUs.
Unfortunately I don’t have enough experience with Qwen 27B to immediately compare, but I do it’s Qwen 3.6 35B A3. It’s much slower obviously but it seems to be way more efficient with its thinking to the point that using it might actually be faster. I find Qwen and some others rehash the same things over and over when thinking without getting anywhere, in mg limited checks here Muse is much better.
I really like the 3.6 35B A3B for experiments, and it seems OK, but as you say, it spins round in thinking loops more than say the 26B Gemma 4 does. If Muse doesn't actually-wait itself as much it will be very interesting.
I am just downloading it to run my small tests.
In my experience it is almost never productively thinking past that point, just spinning in circles. I also reinject all of the thinking. And there are a few tells that it is getting stuck. I have an optional mode that takes the last few turns and tool calls and shoots it off to DSV4 with a prompt to basically understand where it is at and inject better thinking and or planning. It almost always gets it over relatively difficult humps, but some of the time I don't want things going remote. It might end up with 10-30 cents of DSV4 calls over a hours and the quality improvement is remarkable.
The other thing is I trick it into thinking a web_search tool is a web search but it really just asks DSV4 the prompt. DSV4 is a cheap filter to help prevent prompt injection lol. You can give it other models but DSV4 is my cheap-mode default.
edit: oh! My final 35B A3B tip -- use an extremely simple harness. Pi is good. Pi's default tools almost exactly match what Qwen says they tested the model with (likely meaning that tool set is also what they trained it with or something similar). So, in my experience bigger harnesses don't have a noticeable improve ment on tasks.
It had not occurred to me that you could nudge it to stop thinking with a proxy. Nice idea.
Will favourite your comment and come back to it.
ETA: Incidentally you've helped me put into words the difference between the way Muse Glimmer thinks to the way Qwen thinks. There is a clear sense of urgency in Glimmer's thinking traces.
I suspect it will help a lot with enabling preserve-reasoning, because the biggest apparent limitation of this model is the 128K context window.
Though the practical issue I am seeing on my M1 Max MBP is that performance suddenly drops off a cliff if I have DFlash enabled.
The next iteration in LLM products is a 24/7 thinking loop where the claude-code like thing gets input continuously from your wearable, notifications, and newsfeeds and is constantly preparing things for you.
It seems like the purpose of humans isn't to keep machines busy. When our phone or laptop is idle, it's fine if it sleeps. And when we do want something, we'd rather not wait.
(Also, this new model seems to be designed to keep latency down, which is useful for interactive tasks.)
The progress compared to Qwen3.6 27B is good, not that impressive, it's a 4 months old model. (kuto to them to compare to 27B dense and not 35B MoE, it's more fair to do so). It is very probable that Qwen3.8 27B will crush Glimmer-30B on most benchmarks.
It's a dense model, not MoE like e.g. Qwen 35b or Gemma 4 26B A4B. On a Spark it will be memory bandwidth limited
I haven't tried yet (working on it) but back of the napkin estimate puts it at around 15tok/s even after converting to NVFP4. Prefill would be much higher though. That 15tok/sec is pretty typical for dense models of this size:
NVFP4 Q/K/V/O and MLP projections: ~13 GB/token
BF16 attention gates: ~3 GB/token
BF16 LM head: ~2.5 GB/token
Total: ~18.9 GB/token
At 273 GB/s, that gives a bandwidth-only ceiling of about 14.5 tok/s; actual performance would be lower.
> We quantize weights to ~4-bit, bringing the LM under 20 GB. We validated minimal to no degradation on agentic tasks under compression.
https://www.reddit.com/r/LocalLLaMA/comments/1vkgsum/introdu...
I think that if an LLM can't abstract over the differences between Python and C++, it probably will have an even harder time abstracting over the differences between writing code that manages a webserver, and writing code that does aerodynamic simulations.
Some folks on Reddit are having the same experience: https://www.reddit.com/r/LocalLLaMA/comments/1vkm42m/muse_gl...
It uses an order of magnitude less VRAM at longer contexts which is a huge advantage over Qwen 3.6 27B
* total guess
Sure, if you want the latest and almost* greatest. You can pick up an M1 Max 64GB for ~1k.
* I guess 128GB also exists
As an individual, for average privacy needs (e.g. open source or at-home coding and automation), it's pretty much complete nonsense financially to self-host LLMs currently or select hardware now based on the capability to do so, and pay thousands of bucks extra.
The researchers releasing this stuff have almost nothing to do with Meta other than being bankrolled by the slaughterhouse.
You aren't the customer, you are the pawn in big tech's game of thrones. Your good will is a commodity to be traded, almost literally. It will be used against you the moment it's convenient. This is open weights because Meta couldn't monetize it in any other way than to cloud developer's judgement of their reputation.
But I guess most people just don't care.
I'm glad it's open. It does not make me think any better of Meta.
When an American company does anything? Doom. And. Gloom. The engineers? Taken to the slaughterhouse! America? Behind! The public? Bamboozeled!
> This is open weights because Meta couldn't monetize it in any other way than to cloud developer's judgement of their reputation.
I’ve been told over and over this doesn’t matter. Just needs to be cheap and open. Or maybe that’s only when Chyna is involved?
Sorry this post is a bit snarky but it really is something to behold. And certainly I don’t know the OP’s opinions on Chinese open weight models. Perhaps they agree with me.
Let me be blunt and let me say: you don't understand why we people support Chinese models.
1. Chinese labs started with open weight models, US labs started with dooms day narrative
2. US VC based companies must become greedy to win and return the money, Chinese companies can make 1/10 of that revenue and still be happy
3. Meta in this case, started nicely with Llama, then switched to closed models, kicked out researchers to build data labeler CEO empire inside Meta. Now opening again, what's next? closing again?
Regular ppl in the west now hold mildly positive views of the ccp and how 'advanced' china is than usa.
Then there are europeans who now are looking for china to give them the technology handout now that relationship with usa has soured.
Alibaba, Google, Moonshot, Thinking Machines, etc are not releasing their models for free because they love to. They want to grab market share. I'll take it.
I still will not use a hosted Meta product, but damn this model looks solid.
It also has a knowledge cutoff inside this year.
The main limitation is the smaller maximum recommended context.
They're one of 2 companies I would absolutely never work for (weapons etc aside). FB's recruiters hounded me so often I requested that they blackball me. The day they became Meta, I learned this by checking my email to see that they started trying to reach out again. I once again requested that they blackball me. This by extention taints OAI, the other company I'll never work for.
After a few hours with Glimmer I'm pretty impressed. It's better than the benchmark scores seem to indicate compared to Qwen 3.6 27B. I'm very excited for 3.8
Perpetually kneecapped by one of the worst management cultures I've ever seen
Is it worth considering if it's only marginally better than Qwen 3.6 though? Qwen 3.8 27B is almost there, and will probably be better suited as drop-in replacement for 3.6. Not even considering there's probably going to be a 3.8-35B-A3B too - which will have even better performance.
A company is a big thing there's a lot of moving pieces, why do we have to evaluate it as a whole instead of just seeing it as it is?
> being bankrolled by the slaughterhouse.
We all benefit when companies invest their resources in producing open models. No one thinks this absolves anyone of being terrible elsewhere. But we can still be happy about it.
These kind of responses are hilarious.
Someone gives something for free (and indeed this is entirely free) and the top comment is pure complaint.
If a company can spend money to redeem itself then, well, it can (game theoretically or whatever) do whatever it wants in the future and then spend money to wipe the slate clean.
[1] By which I mean: the very act of being prompted to ask such a question, of planting a seed like hmm, Meta might have some aspects which are good for us. You don’t have to be convinced of it. Just the seed itself can pay for itself.
Nothing redeems them at this point of time, they are doing exactly ZERO to redeem. Tossing open weight models (not opensource!!) is not a basis for redemption, and does not constitute remorse in any way. Trying to portray it as such is complicity to META's crimes against humanity.
It has all of the components of a pelican riding a bicycle, though not exactly arranged in the right order!
(For comparison, here are the pelicans I got from Muse Spark 1, 1.1, and 1.2: https://bsky.app/profile/simonwillison.net/post/3mseqv5z4qk2... )
For the same cost, you could run on a frontier model on a pro plan for two years. The economics dont make a lot of sense for this to me, so I would love some input on why people want to do this instead (privacy, for fun, etc).
And in terms of interesting use cases: recently pointed an agent at Blender and gave it vision. That setup can essentially iterate on a scene forever.
A single six year old RTX 3090 works great: https://www.reddit.com/r/LocalLLaMA/comments/1vkm42m/muse_gl...
I fully expect Meta will release other, smaller Muse models in the near future too.
The 5090 is also supposed to be a $2000 GPU, not a $5000 one. The entire market is utterly distorted right now, which will impact cloud inference more and more over time too. They are not immune to the absurdly high RAM prices, so their prices will have to go up over time too until the RAM supply chain goes back to normal.
Prefill: ~1000 tok/s
Decode: 75-100 tok/s
It'll be far faster on a 5090, but I find the above performance to be acceptable. I've seen some claims that it even works OK on an AMD RX 7900XT (~$500USD)
My local NAS is private and I’m not going to send it off to APIs for captioning or metadata; but even Qwen3VL 8B does an excellent job at this, despite being quite old.
They are also really excellent for fine tuning. Unsloth and Tinker (from Mira’s TML) are great places to start.
If your use case is narrower than “coding agent for everything”, you can probably match frontier performances on that narrow domain with ~30b and exceed it with ~100b+.
MoE will be faster because it will read less memory for sure, you still have to have it though.
Fair on size, but the headline numbers are against a model a generation back
It can do that, but its actual selling point appears to be a different take on guardrails and safety alignment.
Either that or the only new training data left was industrial quantities of dark romance literature and Wattpad.
Clever business move. 131k context is more than enough for that use case, and due to that small K/V footprint, you can probably have a bunch of characters on the same GPU.
Or it's just a happy little accident. We will never know.
___
I was informed that normal people use LLMs for mundane tasks like asking for a pancake recipie.
That it apparently can also do decently.
Unfortunately, it is also very confident, regardless of whether it is actually correct.
So maybe it should actually stay the smut engine and nothing else.
- Mark Zuckerberg
Anybody here succeed to run this on AMD?
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 …
https://xcancel.com/alexandr_wang/status/2086756152034066792
It's correct. See the OpenCode demo. Generic models are good enough for coding without necessarily being designed specifically for coding.
Glad to see the extra engineering effort that went into creating this local model and making it run well on a consumer device. I use qwen3.5-coder, and am waiting to kick the tires on this one. I hate to say this, but kudos to Meta ! I hope apple and others follow suit and create similar local models for other use cases like audio, images and video that can run on a laptop.
That's a modern gaming laptop; cheapest I see in the US with 24GB is $3.5k.
Should be quite a bit faster than the new M5 MacBook Pro, and you can run Linux on it!
Waiting on Q3 to download to check speed + do my usual anecdotes. I generate beefy code snippets and poems, and also ingest my HOA declaration and answer nuanced questions.
edit: i should've prefaced this somewhere with: This card ballparks at 800GB/s IO, which I can't seem to find easily on the market anymore. Kinda the ideal card for this model, if I just had a _little_ more VRAM (XTX is 24GB).
edit2: not mtp, this is dflash model (param in child comment). I'm up to ~60 tok/s generation and sitting at 19GB VRAM (i added --no-mmproj (makes it text-only i believe) because I'm used to speculative decoding wanting more VRAM and I'm already close to the limit :sweat_smile:)
edit: My favorite bit of reasoning I saw go by in my "generate me a beautiful code snippet" anecdote: 'Could give a snippet of beautiful code: the "hello world" in brainfuck? No.'
edit2: my first dflash speculative model! no mtp. I'm up to ~60 tok/s on empty context with `--spec-type draft-dflash`
Open weights*
I don't think outside of the Big 3 (Ant, OAI, GDM), given the strong competition from China, any other Lab has a chance at capturing the coding market if they aren't open weights (save for xAI whose latest Grok looks every bit good & will probably rely on Cursor for distribution instead of going open weights). There's literally no other selling point, as the capabilities have mostly converged by now among the chasing pack.
It’s not completely open source, but they actually release their pretraining and post-training datasets with some redactions for (cough) pirated content.
They also have very good code and playbooks for actually doing a fine-tune, CPT, etc.
Even if you’re not tuning a Nemotron model, its mixes are very excellent for your replay data slice; or general experiments. Way better curation and quality than Dolma, etc; or other large huggingface data mixes I tested.
Dense model makes it dog slow on anything without HBM. Max 15tok/sec on decode on DDR5 systems like a Spark or a Strix Halo -- and that's at 4 bit quant.
I would hazard a guess that fast small models with a smart agent harness can do quite well compared to large models which cant be run locally.
I agree with their open-source model approach, but actually trusting Meta… to protect my privacy and my data… when it’s running on my personal hardware…
Not . In . A . Million . Years - that ship has sailed
https://github.com/pytorch/executorch/tree/main/examples/mod...
I'm all for it though, and I think Glimmer is a fantastic bet on locally-hostable models. I for one would love to self-host as much as I can.
I don't know why MSL released this, but it is very nice that they did.
> 3/ muse glimmer was developed with its own architecture and recipe, optimized for its size and agentic performance requirements.
This means we're in the endgame does it not? If the architecture was NOT optimized for intelligence ...
Like, in the car wash test, this was in the thinking traces:
“Walking won't get the car washed.”
and:
“Perhaps answer: Walk if you want to wash yourself? No”
Which made me laugh out loud.
Even in the final answer:
- - -
You have to drive it. Walking 50m won't get the car clean, it'll just get you to the car wash.
If you mean you going to the car wash to check prices / pay / get a brush, then yeah, just walk the 50m. It's about 30 seconds on foot and you save the cold-start emissions of firing up the engine for a distance you could roll.
If you mean the car itself getting washed, the car needs to be at the car wash. You can push it 50m for a workout, but driving it 50m is the practical way.
- - -
The emphasis on "you" was from the model. I mean I write like this so I can't judge its tone harshly :-)
ETA: The knowledge cutoff is January this year, so it didn't encounter car wash discourse in the scraped training set, though I suppose you can't rule out some kind of fine tuning to deal with this scenario. Still made me chuckle.
ETA 2: obviously I wrote this before you added your last paragraph. WTF dude.
Product teams really need to hire at least one or two people with a 12-year-old's sense is humor. They need to winnow all the potential stupid jokes out of their product namings.
> Amazing! You have a total of 128.94 TFLOPS of computing power. 71.3% percentile on scale of "GPU Poor" to "GPU Rich"
The way I see it, these are amazing machines that the richest folks are hovering up. I think they should be in the hands of regular people as much as possible. They depend on an incredibly global, increasingly fragile supply chain. If the become impossible to produce, their value would increase tremendously. I think they will become really valuable to you to use the tokens directly, but if that isn't the case, they can be rented out or resold. Please don't just buy any hold. Let's try to get as many people that can use them for decent things that help humans. For example:
https://spectrum.ieee.org/small-language-models-ai-pharmaceu...
Photoshop source code+ OSI license = open source
Photoshop binary you can run on your own computer = open weight
Photoshop SaaS web app = closed, proprietary (Opus, GPT, etc.)
"Open weight" models are still just binary blobs that are completely inscrutable. It's like bringing home a dog from the rescue and just hoping that it doesn't have a tendency to bite kids in the face. You just can't know. The only thing that you can do is try to add more training (fine tuning) telling it not to bite kids.
I don't think the FOSS community has ever accepted this, but somehow we're feeling like it is okay now.
Photoshop binary you can run on your own computer = open weight
I don't think this is a correct analogy. You are not allowed to distribute modified versions of the Photoshop binary. Most open weight model licenses allow you to make and distribute your own finetunes, etc.
Sure, having information about how these models were trained is helpful for reproducibility, but it is basically impossible for anyone without substantial capital and access to the same (likely copyrighted) data to reproduce the model. For normal users, owning the model weights essentially means owning 100% of the model, you can inspect and study the weights in much the same way as the lab that produced the model can, you can modify the weights, and you can use and distribute them if the license allows you to
Given an open weights model trained to never bite kids, you can get it to bite kids with 10 prompts and a linear projection, the known simple algorithm doesn’t even need a backwards pass.
yay asymmetry!