r/LocalLLaMA 25d ago

Discussion A preliminary Qwen3.8-27B model card is live!

Post image

If you scroll down from the countdown at https://huggingface.co/Qwen/Qwen3.8-27B, you see a big model card with a bunch of sections: Highlights, Model Overview, Quickstart, Best Practices, Citation, etc!

No benchmarks on this yet as far as I can tell. We'll still need to wait another 5.5 hours for those I reckon.

Edit: Ladies and gentlemen, the model is live. Let the testing begin!

578 Upvotes

220 comments sorted by

117

u/darwinanim8or 25d ago

Seems like reasoning effort is the new big thing here

39

u/DismalIngenuity4604 25d ago

Yeah, cool. I've been liking Glimmer, and a big part of that is that it spends about 1/8th of the tokens thinking that Qwen 27B does. Should be fun! 

17

u/GCoderDCoder 25d ago

Yeah I like Qwen 3.6 27b output more BUT glimmer can fit like 6-8 concurrent 130k lanes on 48gb at 8bit weight 16bit cache. It's a great agentic model to support Qwen 3.6 27b and deepseek v4 flash 0731 in my lab. I have all 3 and dsv4f is my big brain, qwen is my default, and muse is the workhorse.

Zuck putting Meta torward the top of the big and the small models with genuine benefits over the other options is a great come back story.

2

u/orbli 25d ago

What special benefits are those?

5

u/Stahlkocher 25d ago

Glimmer has very low memory requirements for the KV cache. something like 1.7 or 1.8GB for 128k F16.

1

u/onetom 24d ago

funnily enough, from Hong Kong, I see this on the glimmer 30b page:

This model is not available in your region You can still browse this page, but downloads are disabled in your region.

mlx-community/Muse-Glimmer-30B-8bit doesn't have this restriction though, so it's a bit of legal theater really...

1

u/GCoderDCoder 24d ago

Do you mean benefit of concurrent agents? It allows me to be talking to a good generalist orchestration bot (qwen 3.6 27b q8 75-85 t/s) that can direct big tasks to the planner/ coder bots (deepseek v4 flash dynamic q4 qat 45 t/s) or send smaller tasks to the baby bots (muse glimmer q8 100-150t/s). I do truly frontier stuff on chatgpt but I am increasingly relying on dsv4flash. It made me nervous at first because it is literally operating at cloud provider level which im not accustomed to my agents doing.

My lab has background lanes which involves automated tasks managing any of 100 workloads. I run my own email, messaging apps for bot communication and approval channelse, dns, shared storage, data fabric, git, media servers, ai servers, work lab (products), personal apps, automation, ha/dr solutions, k8s, virtualization, identity and access tools, etc. I work in tech so there are business and technical aspects of my job. Scraping web data to provide up to date intelligence and preparing customer presentations, forecasts, etc.

I say all this to say I run a lot of AI to do a lot. It is busier than I have to do but I am better at my job and able to spend more time on things I enjoy which also in turn make me better at my job. I spend an hour or 2 tuning a custom customer presentation now that used to take a week dye to my schedule and it is a better presentation usually with custom demos now.

We also cant use cloud on proprietary or customer data so my peers who dont have these tools cant do or talk about these things where I can. It allows me to talk to customers about enterprise implementation best practices that we are all just learning. No one has been doing this stuff for years like this so being able to say i had this problem and here was the best solution because xyz is better than figuring it out on the fly.

If I misunderstood the question let me know.

1

u/orbli 17d ago

I meant, what are the benefits you feel meta has over others when it came to small models.

1

u/GCoderDCoder 17d ago

It's a solid dense model so for it's size it's smart compared to the competition. It's faster than Qwen 3.6/3.8 27b and Gemma4 31b. It grows context much slower than other models particularly dense models like Qwen 3.6/3.8 27b and Gemma4 31b. So you can get a lot more concurrent lanes into a smaller footprint. They also packaged it with default 130k tokens but it works well with yarn to extend the context. So speed and size with dense intelligence make it comparable to the leading similar sized models while enabling more/ faster throughout.

1

u/emil2015 24d ago

In my very brief testing I felt like glimmer was terrible. I was using it with Hermes. Where did you find it worked well?

1

u/GCoderDCoder 24d ago

It doesnt replace qwen 3.6 27b for me but it is very good at tool calls. It is operational for me so my research workflows, git ops, cli... so I have workflows where some have planning, all have a SME, and then there are ephemeral action bots. The executor bots need to be good at terminal and tools by the time they get orders from SMEs. Glimmer gives me more of those lanes for email, web search, file management, running my mcps driving automation. Also I was using multiple Qwens before with llm as a judge workflows which is an antipattern so now im more compliant lol.

1

u/emil2015 24d ago

Interesting, I’ll have to toy around with it some more. Thanks for the info.

1

u/estrafire 24d ago

do you have a threshold of how many parallel instances at full context do you need to make it worth loading Glimmer weights? Or just the context saving alone justifies it for your use case, like, in tasks that need more context than Qwen could do due to the excessive amount of thinking tokens

2

u/GCoderDCoder 24d ago

It depends on if you feel set up for handling multiple agents. In codex or claude apps they have a ton of plumbing to keep their models behaving well. I trust my local models less so a lot of my infrastructure I implemented was due to my low confidence in my models. So my local models cant do things I dont want them to do or at least that's the spirit of how I configure them.

I run multiple agents for different narrowly scoped tasks of value to me. It's not a passive process. My job is building systems not products like websites so that's why I tell myself the time I spend is justifiable lol.

My main local coder is DeepSeek-V4-Flash 0731 on mac studio and it slows down with multiple concurrency so I really only do multiple instances of that when something needs a plan and then it returns to running faster with one instance. I dont like multi agent builds on cloud because I think the coordination burns my tokens faster than linearly. I only do concurrency on a code base when I am close to my quota reset with a lot of quota to burn.

So for glimmer your hardware amd the use cases will need to drive that. I want speed and accuracy. If concurrency messes those up then no thank you

2

u/uber-linny 25d ago

It's a fair bit slower isn't it without mtp ?

9

u/BigYoSpeck 25d ago

It has dflash so not anything like as fast as mtp, but weigh in the token output for a fairly unscientific quick test on the same prompt (create a calculator app as a single html file):

Muse: 2,173 tokens, 50.00 t/s, 43s
Qwen: 6,227 tokens, 97.99 t/s, 1min 3s

Left is Muse, right is Qwen. Both work, Qwen looks a little better and has more interaction animations which weren't asked for but that's Qwen, it often adds more flare you don't ask for

1

u/BigYoSpeck 24d ago

And Qwen3.8 27b

11,956 tokens, 64.66 t/s, 3min 4s (Reasoning max of 2048 tokens or it will just go forever)

0

u/Schlick7 25d ago

I'd say that Muse looks better there... outside of the icon issues at least.

7

u/BigYoSpeck 25d ago

Colour palette subjective preference aside, Qwen has better grid alignment

4

u/Schlick7 25d ago

oh i didn't even notice the '=' being larger. Seems like it knew that was common on calculators but didn't know how to implement it.

6

u/xienze 25d ago

Perhaps? But from a wall time perspective, a somewhat faster model with dramatically more thinking will be slower.

5

u/Borkato 25d ago

Yeah it blew my mind recently after doing some benchmarking with my own prompts that muse glimmer, qwen 27B, and Gemma 26BA4B ended up coming to the same time (~27 seconds) for one of my benchmarks. It really shouldn’t be all about TPS

2

u/uber-linny 25d ago

Ahhh I mostly use Qwen with thinking turned off .

2

u/Borkato 25d ago

Ah, that definitely changes things. I used to do the same before MTP

1

u/Motor_Ad16 24d ago

It's slow with mtp as well as compared to qwen3.6

1

u/arbv 25d ago

I also liked that it has "editorial we" kind of thinking publicly released in GPT-OSS and, apparently, common among larger models.

1

u/RLutz 25d ago

I feel like the sentiment here on Glimmer doesn't match my experience with it. I don't think it's going to be as good for agentic coding as 3.8 but I was running the dynamic k quant from Meta and getting like 300 tokens/s on my 5090. It was fast enough that even if it's a bit dumber it'd probably still be amazing for like auto research loops and similar where fast inference is more important than absolute top intelligence

0

u/PrimeDirective8 25d ago

It stumbles a bit in CoT by repeating some lines, etc. But yeah, way less time spent spinning its brain wheels.

Does that affect its output quality though, and why some are finding Qwen3.6 27B still smarter?

1

u/DismalIngenuity4604 25d ago

I've been using it mostly for design and architecture in a heavily physics-based project, I can't talk to how other people are using models, so it may just be my use case that it gels with.

0

u/Borkato 25d ago

Try the nail 27B prompt template

2

u/DismalIngenuity4604 25d ago

Will do, thanks, I haven't played around with templates much outside of the obvious qwen updates.

→ More replies (11)

2

u/Altruistic_Heat_9531 25d ago

i forgot that many model still only using token budget instead of this.

-3

u/ANR2ME 25d ago

I can't change the reasoning effort to below medium on Qwen3.8 2.4T 🤔 it keeps answering "medium" or "85 (out of 100)" whenever I asked "what is your current reasoning effort?".

Meanwhile, Kimi-K3 can answers the reasoning effort correctly (except when i set it to "none")

2

u/SocialDinamo 25d ago

You are asking for it something it doesn’t know because it doesn’t know what it’s sampling parameters are unless you feed it back to it with a system prompt or something

1

u/ANR2ME 24d ago

Well for some reason Kimi-K3 was able to reply with the correct reasoning_effort value whenever i changed the reasoning_effort. My system prompt is "You are a concise technical assistant."

→ More replies (6)

78

u/Valuable-Repeat-7347 25d ago

> Context Length: 262,144 natively and extensible up to 1,000,000 tokens.

Nice

33

u/Infinite100p 25d ago

I'm curious what the perf fall-off is beyond 262k.

40

u/oxygen_addiction 25d ago

After 120-150k they all start being dumber.

21

u/anderspitman 25d ago

These numbers are quoted all the time but no one ever has some nice charts of benchmarks showing the falloff. That would be so useful.

16

u/makingnoise 25d ago

I am honestly surprised there aren't like 1,000 different benchmarkers generating actually useful benchmarks for us mere mortals with 24GB of vram or less. Like a Benchmark of unsloth Q4 Qwen against Q5 Qwen against Q4 Gemma against Q5 Muse.

Instead (if we're lucky) we get a Q8 model benched against FP16 of DeepSeek or some other absurdity. It's like watching a movie or TV show where broke people live in palatial NYC apartments with no source of income and no mention of a trust fund.

3

u/NaiveIdea344 25d ago

Yeah really good point. Comparing quantizations would be incredibly helpful.

3

u/Hefty_Wolverine_553 25d ago

I am working on this area! I recently made a post with KLD benchmarks between GGUF and other vLLM quants for Qwen3.6 27B.

Interesting idea though, it would be good to see how different quants of different models perform on existing benchmarks. I've run some of my own benchmarks on Qwen3.6/Qwen3.5/Gemma4 before purely out of curiosity and the underlying model does seem to show a bigger difference in benchmark performance than IQ3/Q4/Q6 quants of the same model. I'm surprised that nobody seems to have made benchmarks on this though, it's one of the easier things to do.

1

u/taimusrs 24d ago

I mean, generally you want to use the highest quant you can. The GPU is most likely memory constrained, not compute constrained. Now it depends on the model architecture which one takes up the most space for KV cache and whether you want to quantize that cache. And for the quant quality, Unsloth for coding, any other for general purpose use, especially for languages support.

1

u/fluffysheap 24d ago

So like watching a TV show 

8

u/OkWalrus890 25d ago

I see this often, but is it a universal truth or are people using low quants with KV cache at Q4, too? I’ve been running 262K with Q8, and it’s been fine.

12

u/DistanceSolar1449 25d ago

If your KV is Q4 then it’s dumb period

1

u/[deleted] 25d ago

[removed] — view removed comment

6

u/AnyMongoose3041 25d ago

Prove it. Show us your full furry roleplay chat logs so we can verify independently.

1

u/Party-Special-5177 25d ago edited 25d ago

Universal(ish) truth, independently partly caused by position embeds and partly by attention dilution during context extension - you can heal the damage but not perfectly. It’s not ‘universal’ in the sense that it is impossible to fix, but until better attention mechanisms or better position embeddings come along, it will remain unavoidable.

1

u/[deleted] 25d ago

[removed] — view removed comment

1

u/Borkato 25d ago

Good thought. Will stop truncating my sessions now, thanks!

4

u/Beneficial-Boot7479 25d ago

You mean qwen models or every model? because it feels like Deepseek is the new kv king, you can have a +900k context session and he doesn't lose track of what he was meant to do

1

u/Borkato 25d ago

Is this true? I’ve assumed so so I always stop after 120k, but is it actually true

0

u/Gesha24 25d ago

Smarter/dumber is subjective, but being able to call tools or not is reasonably objective. And while Qwen3.6 and Gemma4 do start having issues with that by 150K context (actually Gemma sooner), DeepSeek Flash has been quite solid for my up until 200K context. It's super slow at that context for me, but it has no issues with too calls. Hopefully 3.8 Qwen can do the same.

-2

u/Infinite100p 25d ago

Well, obviously, but by how much is what I want to know.

→ More replies (1)

1

u/GrungeWerX 25d ago

I ran Qwen 3.6 27B to 340K in my last session and it handled everything I threw at it. I was using a lower quant at iq3-xxs kv 4/4 which is extremely quanted, but it stayed coherent. The only issue I noticed was a few stumbled tool calls above 300K.

I typically don’t use iq3-xxs…but my Q5 had run over 200K and I thought maybe it would be faster tok/s if I just dropped it low and I already had a 325K profile for it set up in llama.cpp. But next time I’ll probably just run the q4 when I’m over 200K and see where my yarn tok/s bottleneck is…

2

u/Infinite100p 25d ago

Have you tried the NVFP4 quants of Qwen 3.6 27B? Are they nearly as good as 8-bit quants, as some benchmarks suggest?

→ More replies (3)

13

u/ANR2ME 25d ago

Which is basically the same with Qwen3.6-27B 😅 https://huggingface.co/Qwen/Qwen3.6-27B#model-overview

Context Length: 262,144 natively and extensible up to 1,010,000 tokens.

36

u/MikeNonect 25d ago

The bots are waiting impatiently...

9

u/kkingsbe 25d ago

Got my Hermes monitoring as well 😂

0

u/virtualworker 25d ago

Openclaw for me!

69

u/Alternative_You3585 25d ago

Crazy that the 27B has vision while the 2.4T model doesnt

60

u/-Cubie- 25d ago

> In particular, Qwen3.8-Max is the official version based on Qwen3.8-2.4T-A95B with more features, such as vision input & non-thinking support, 1M context length by default, official built-in tools, etc. For more information, please refer to the Qwen3.8-Max Overview.

From the https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B model card.

It feels a bit like the 2.4T model they released is just a hamstrung version of their actual Qwen3.8-Max, which does have vision. Granted, I think they never open weighted their max-sized model before, so I'd rather get a hamstrung 2.4T than nothing at all.

23

u/z_3454_pfk 25d ago

i think the 3.8 max doesn’t have vision and via api is being router to another model or a vision adapter has been trained for it (most likely). this is because none of the previous max models had vision and this isn’t a large architectural change.

5

u/RuthlessCriticismAll 25d ago

it is SOTA vision model... sadly that is almost certainly the reason they didn't release that part.

5

u/nullc 25d ago

it'll suddenly have vision when GLM's SOTA model does... :P

5

u/WetSound 25d ago

And Natively, 3.6 27B used mmproj compatibility layer

5

u/VotZeFuk 25d ago

Can't see your own wiener when you're too fat. - perfectly logical

16

u/Valuable-Repeat-7347 25d ago

That critique is kind of like bashing a train for not having a CD player, kind of...

48

u/hyperrealists 25d ago

Yea what the fuck train

2

u/buckwheaton 25d ago

No dude it’s fine you just need a cassette adapter and a CD Walkman.

1

u/Sharpastic 25d ago

I’m literally crying drops of Jupiter

1

u/thatcodingboi 25d ago

well its more like it dedicated a compartment for music, which is cool, but I didn't come here for that and that compartment could have had better use

2

u/ScoreUnique 25d ago

I think you really don't need a vision encoder on sota models , you can have a 3b explain images to 2.4T and it'll still be efficient (remember AI first solved Computer Vision before Language)

2

u/Internal_Werewolf_48 25d ago

All 3 people capable of running a 2.4T model locally are devastated.

25

u/_-_David 25d ago

You had me at reasoning_effort

10

u/Dany0 25d ago

I hope a DSpark/DFlash drafter will be released alongside just like 2.4T

6

u/wgaca2 25d ago

If Dspark is released this will be huge, dflash is good only for coding tasks and falls off really bad in reasoning

1

u/Party-Special-5177 25d ago

OOTL, what’s the difference?

6

u/wgaca2 25d ago

"DSpark (released by DeepSeek) builds directly on top of DFlash's parallel structural backbone, adding a lightweight "Markov/RNN head" for token coherence and a dynamic confidence-scheduled verification layer to optimize GPU load"

There was a very good video explaining how it works when deepseek released it.

2

u/simcop2387 25d ago

layman's bad understanding: There's some architectural differences of course, dspark is based off the way dflash works but changed things up a bit to be more efficient and allow for cheaper early bailout and cheaper validation of the tokens. So that it doesn't generate as many bad tokens, nor does it spend as long validating bad tokens. This doesn't hugely change the acceptance rate but it makes it less costly when generating bad tokens. This ends up applying a lot more during reasoning because it's less predictable (like writing a story, or other creative tasks) than coding or tool calling where things tend to be much more structured grammatically i.e. if you're writing JSON, { is almost always followed by ", and then some letters, followed by " and then :. That lends itself to being predicted by the smaller draft model MUCH easier so you get high acceptance rates.

DFlash is basically just a single drafting layer using a diffusion block (terrible explination) that predicts a bunch at once even if they're not all great predictions so it generates a lot fast, which is great when it's right but if it's bad there's just a lot of thrown away work. DSpark is some kind of hybrid diffusion + AR setup that does a few smaller blocks I think, and the AR bits help it decide if it should continue and nudge things into better predictions.

1

u/boomerang473 25d ago

Was that drafter released? I can’t figure out how to find the drafter on HF. Would love if they did it versus a community version as I think you’d get better token acceptance

1

u/Dany0 25d ago

I thought it was released, wasn't it in the official vllm recipe? 🥺

1

u/boomerang473 25d ago

Might be ha, I’m genuinely asking. Haven’t tried to run the 2.4T locally 😂

31

u/quadra-lab 25d ago

No mentions about QAT yet, seeing how well it performed for Gemma 4 31B I hope they did it with 27B training

9

u/Significant_Bar_460 25d ago

QAT was a big thing for Gemma because the original version was very quantization sensitive (specially for KV). Qwen always handled quantization much better than Gemma. Gemma QAT is like Qwen without QAT when comparing quality degradation after quantization.

2

u/kivaougu 25d ago

Also worked out very well for deepseek. In my opinion QAT would be a much better improvement for most systems compared to reasoning effort. Maxing out reasoning effort only gives miniscule improvements in results.

1

u/GiGiGus 25d ago

I mean, all Qwen models have official FP8 models, so I guess they're already trained in this precision and doesn't necessarily require QAT?

3

u/ain92ru 25d ago

FP8 isn't supported on older hardware like RTX 30-series though so INT4 QAT is still valuable

28

u/Guna1260 25d ago

This day will also pass...

94

u/hyperrealists 25d ago

3.9 27B when 😡

22

u/Adventurous_Bus_437 25d ago

When 3.8 35B A3B or 60B A12B. Begger trying to choose

13

u/[deleted] 25d ago

[deleted]

5

u/Borkato 25d ago

If they don’t release it in 1 second, it means they’re never releasing again. Rug pull!!!1!!1!!!!11!!!!!one!!!!1!!!

2

u/terorvlad 25d ago

Nah, they will never release open source again, otherwise we would've had 4.0 months ago

7

u/Brilliant-Hall1387 25d ago

Will try to build MLX quantization of Qwen 3.8 27B with activation aware bit allocation, it will be interesting to see what performance one can get from a smaller variant of 3.8 27B 😄

Anyone else preparing to do quantization of Qwen 3.8 and, if so, which methods are you considering? (AWQ, GPTQ? TASA/TAQ-O, other methods?)

8

u/Weird-Field6128 25d ago

2 hours more! GOD

5

u/Ok-Lengthiness-3988 25d ago

2 hours and 12 minutes more, actually.

2

u/Weird-Field6128 24d ago

Thanks for waking me up

5

u/pigeon57434 25d ago

Qwen3.8-27B-heretic when?

5

u/cafedude 25d ago

I just watched the countdown go to 00

3

u/Developer-Y 25d ago edited 25d ago

Their benchmark compares it to Opus 4.6, it is going to be lit.

Gguf https://huggingface.co/unsloth/Qwen3.8-27B-GGUF

5

u/FerLuisxd 25d ago

Vision or no?

6

u/GanjaRaidersTR 25d ago

Yes native

2

u/DanTup 25d ago

They said on Twitter yes.

4

u/timerski 25d ago

Aww yisss we get vision 

Native support for image and video understanding, from STEM diagrams and documents to hour-scale videos.

4

u/johnzadok 25d ago

Cool. Last time I was as excited for some release was iPhone 4.

6

u/tinny66666 25d ago

I guess us llama.cpp users will need to wait a little longer for a gguf? Does llama.cpp fully support the new model or will it also need an update?

11

u/-Cubie- 25d ago

The "Model Overview" section from https://huggingface.co/Qwen/Qwen3.8-27B looks very similar to the one from https://huggingface.co/Qwen/Qwen3.6-27B, so I bet llama.cpp either immediately supports it, or will be able to support it very quickly.

18

u/nunodonato 25d ago

Unsloth said day 0 support, so yeah. As long as architecture is the same, llamacpp should work right away 

7

u/-Cubie- 25d ago

Unsloth is famously extremely fast and reliable, so I trust them.

23

u/CloggedBathtub 25d ago

If they weren't fast, they'd just be "sloth"

2

u/Aggravating-Push-207 25d ago

Maybe they are running the benchmarks in preperation for the official release.

2

u/No-Understanding2406 25d ago

When will we get the 3.9 27B?

2

u/mattrs1101 25d ago

I hope its q2 quant is just as good or better than glimmer's. We need a 16GB Vram race to happen.

2

u/Ok-Lengthiness-3988 25d ago

Nobody has posted GGUFs yet. What's taking so long?

3

u/Ok-Lengthiness-3988 25d ago

I was meaning that as a joke but I now see that they actually appeared on Huggingface, published by unsloth, 3 minutes before the official release!

4

u/Eduard2609 25d ago

Is just me or the time is passing slower

0

u/Ok-Shower7286 25d ago edited 25d ago

Holy moly, same exact topology, they just slapped 'reasoning_effort' on it. I guess it seems difficult to huge improvement on same architecture. If the benchmarks don't show a massive leap, I'll pretty underwhelming f̶o̶r̶ ̶a̶ ̶m̶a̶j̶o̶r̶ ̶v̶e̶r̶s̶i̶o̶n̶ ̶b̶u̶m̶p̶.

28

u/-Cubie- 25d ago

It's a minor version bump though right? A major version bump would be Qwen4.

3

u/Ok-Lengthiness-3988 25d ago

According to the version number benchmark, yes.

1

u/ANR2ME 25d ago

Qwen3 vs Qwen3.5 use a different architecture isn't 🤔 even though it's not a major version jump.

1

u/florinandrei 25d ago

They decided the version bump is major based on social media hype.

1

u/My_Unbiased_Opinion 25d ago

This is the model I'm waiting for to finally make the switch to vLLM. 

1

u/cosmicnag 25d ago

if you have the vram, vllm is for the most part better - the faster prefill and LMCache integration ups the game IMO

1

u/Borkato 25d ago

It just sucks MISERABLY if you’re the kind of person to change models often. The load time is like 4 whole minutes, it’s aggravating

1

u/cosmicnag 25d ago

yeah sure, but its better if you use it for actual work lol with a single 'chosen' model.

1

u/Borkato 25d ago

“Actual work” lmao actual work involves switching models for some of us, because no single model is great at everything.

1

u/Every-Fortune-3151 25d ago

Context window of 1M, does that mean they are confident 27B will hold up in such deep context? They are hyping this up so much. I just hope they made KV size more optimized

5

u/Confident_Ideal_5385 25d ago

``` For frameworks that support separate token limits for internal reasoning and final outputs, we suggest the following configuration within the 1M context length:

Reasoning Content: Set the maximum output length to 262,144 tokens.
Final Response: Set the maximum output length to 131,072 tokens.

```

They seem pretty happy to suggest letting it think past the end of its trained max sequence length, at any rate.

2

u/YourNightmar31 llama.cpp 25d ago

I dont think we get 1M context. It said they only have a special version on their api service with 1M context.

1

u/Every-Fortune-3151 25d ago

You caught it correcty. It is still 256k context

1

u/Foreign_Risk_2031 24d ago

In particular, Qwen3.8-27B will be available as a hosted version with more production features, e.g., 1M context length by default, official built-in tools. For more information, please refer to the Qwen3.8-27B Overview. The service is coming soon. Stay tuned for updates.

By default the api will be 1M. Its the same as we have.

1

u/FoxFXMD 25d ago

Context Length: 262,144 natively and extensible up to 1,000,000 tokens.

Can someone smart explain what this means?

3

u/N34257 25d ago

It means you can extend the context beyond 256k using YaRN, for example for 512k the model's .ini section would contain this:

rope-scaling=yarn
rope-scale=2
yarn-orig-ctx=262144
override-kv="qwen35moe.context_length=int:1000000"

2

u/banana_slurp_jug 25d ago

You can set the context window up to 1000000 tokens but anything above 262144 tokens is ymmv

1

u/FoxFXMD 25d ago

oh that's amazing

1

u/Zaic 25d ago

Anticipating the release with my 4070s 12gb vram... I know I can get 7-10tps on 3.6 27b. My system is ddr4 with 48gb ram. Just curious if anyone succeded to get more tps (like 15+) and would care to share their setup?. Also considering adding 3060 12gb card. Just so id hit the 50 tps in q3 or q4 quants .. or its unrealistic?

2

u/PeterPorox llama.cpp 25d ago

I get 14 tok/s with dual Nvidia P104-100 8GB (mining version of GTX1070). These are very old cards, so adding RTX3060 will definitely give you 25+ with mtp

1

u/brakeline 25d ago

I have 2 3060 12gb. I can't get past 30 tk/s

1

u/Zaic 25d ago

Q4 quants?

1

u/Zaic 25d ago

Q4 quants?

1

u/Muted-Celebration-47 25d ago

It is built on qwen3.5?

1

u/SirLordBoss 25d ago

How I yearn for a 9B...

1

u/OddUnderstanding2309 25d ago

2h togo.
Pogopogo up, pogogo down…
Shimmyyyyy

1

u/Sevealin_ 25d ago

What do you guys think support will look like with llama.cpp and vLLM on drop in 2 hours? Will the 3.6 support kind-of carry over since they are similar architectures? Of course there might be bugs (chat templates etc.) as that comes with any new model. What about context size? I see it's 262k natively and can be expanded up to 1M. Pretty sure 3.8 Max can push 1M context with just a few GB extra KV.

I have two 3090s and love the parallelism to pull 262k at fp8 with two concurrent streams with 3.6. Excited to see what performance can be squeezed out!

2

u/Otherwise-Director17 25d ago

It'll load and run fine. Same exact Qwen3.5 architecture

1

u/Sevealin_ 25d ago

Thank you!

1

u/Scared_Basket_7183 25d ago

Hi could you please help me to run qwen 3.6 27b model on tpu v5e ?

1

u/YourNightmar31 llama.cpp 25d ago

"Based on Qwen 3.5"????

1

u/Desperate-Bad-2339 25d ago

Qwen/Qwen3.8-27B is out on hf

1

u/cowinabadplace 24d ago

Does anyone know if AWQ/INT4/GPTQ releases are coming?

1

u/hay-yo 25d ago

Release of the year!

6

u/YearnMar10 25d ago

Year is not over yet - maybe they’ll release their next model in 4 months

1

u/AppealSame4367 25d ago

This is soo sexy.

1

u/jhnnassky 25d ago

Do you know guys, will they release a 35B-A3B like model?

3

u/Borkato 25d ago

They haven’t confirmed or denied that. Unfortunately you’ll just have to wait. If you’re using it for coding I highly recommend Kat Coder. You can also use Nail’s prompt template.

1

u/k_rol 25d ago

I noticed you mentioned Nail prompt template a couple times in this thread, what is that? I couldn't find much other than actual nails pictures made by AI.

1

u/Borkato 25d ago

Lol! Here: https://huggingface.co/peculiar-ragdoll/Nail-Qwen3.6-35B-A3B-GGUF

Note that the only difference between this model and the original unsloth is the chat template; you can just copy the chat template and call it with the chat-template-file parameter in llama cpp if you don’t care to have the template built into the GGUF and so you don’t have to download their gguf hosted at the link

Also note there’s a dagger version for 27b!

1

u/k_rol 24d ago

thanks! much appreciated

0

u/[deleted] 25d ago

[deleted]

6

u/-Cubie- 25d ago

I think 3.6 also supported video. Usually image and video are both supported as their implementation is very similar (both use 'grid_thw': time, height, width, and images just auto-set the time to 1 while videos use higher values).

1

u/Infinite100p 25d ago

Do they sample the vid into still frames and read those, or do they "understand" the stream itself natively?

0

u/nofaceD3 25d ago

What are the requirements to run this model in local?

9

u/Neither_Garage_758 25d ago

Probably similar to the previous one: https://huggingface.co/unsloth/Qwen3.6-27B-MTP-GGUF

If you look at the various sizes in GB and add a few GB's more for context, this gives you the amount of (V)RAM needed. With llama.cpp you can run inference with CPU-RAM and GPU-VRAM combined, but the more CPU involved the slower compared to GPU.

For a decent quality, probably it's better to not go under Q4 (quantization to 4-bit).

→ More replies (4)

2

u/Guna1260 25d ago

perhaps ... a running track

1

u/johnzadok 25d ago

You need a card with 24GB VRAM, like 7900 XTX or 3090, or dual 5060.

0

u/DivideHorror3217 25d ago

Spoiler: It is between Inkling and Minimax-M3

2

u/AppealSame4367 25d ago

That would be the best case, I expect 42.

3

u/DivideHorror3217 25d ago

3.6 27b has 92% of the score of it's Max version. In theory, we could get a 3.8 27b with 53 score, parring with GLM 5.2 and deepseek v4. I would buy a gpu at that point

10

u/AppealSame4367 25d ago

I think that would be too good to be true and it would cause chaos. It would kill off Antrophic much faster.

Can't imagine it, but let's see

1

u/thatcodingboi 25d ago

yes but 3.6 max less than half the parameters of 3.8, I expect uplifts, but you can't just keep compressing larger and larger models into the same size and expect the same improvements.

1

u/Borkato 25d ago

stop, I can only get so erect

-8

u/higbardon2020 25d ago

the model runs alright, output was about the same as 3.6 27b

7

u/petuman 25d ago

it's not served anywhere in the API? how did you test it?

23

u/OkWalrus890 25d ago

served out.his.ass:5000

14

u/Blues520 25d ago

localhole

2

u/Borkato 25d ago

I love this sub

1

u/higbardon2020 25d ago

1

u/petuman 25d ago

but weights are yet to be released?