Works well, comparable to Qwen 3.6 27B and then some

#36
by Omnomynous - opened

Ran the BF16 variant from unsloth on my M2 Ultra 192GB. Gets about 14tok/s, but more importantly, maintains that speed throughout the entirety of context. Very usable for coding tasks. Shorter reasoning chains than Qwen 3.6. Also seems to prefer to make smaller, more surgical edits. I'm seeing more tool calls with shorter edits. Gets more done in 128k context than Qwen, but the limitation to 128k is a disappointment when the competition all now use 256k windows.

Has one HUGE advantage over qwen 3.6 27B, at least on my setup, and that is that it doesn't seem to need to prefill after a long searies of tool calls and thinking. On Qwen, if it finishes a task at 50% context and I want it to continue on to something, I'm in for a prefil wait up to a few minutes. With Glimmer, it responds and springs back into action with basically no wait. Impressive model, hamstrung by a non compteitive context limit.

Will still be using Qwen 3.6 35B MOE for my "daily driver" because the speed is so much better, but this will probably replace the 27B variant for the hard to scratch bugs and technical problems.

Nice job Meta team! Glad to see you guys back in the game. Was getting a little one sided around here with everything good made in China lately! You've still got the chops. Now keep it going! Give us a full fat 256k context, and an MOE speedy boy when "good" is good enough. :)

https://huggingface.co/meta-models/Muse-Glimmer-30B/discussions/22
yarn works -- i get 262k context on my 2x rtx3090 on unsloth q8kxl
may be you can try on your side to confirm!!

I think this model is better than Qwen 3.6 27B. It analyzes the source code architecture more deeply and doesn't speak inarticulately like Qwen.

I noticed that Glimmer keeps researching(command, read, grep etc) without results while Qwen found answer in five steps(used internal tool and then just read needed files and based on own knowledge proposed solution). It is good that Glimmer knows that there is no answer in context but it needs smarter research logic and usage of available tools.

Sign up or log in to comment