#Alibaba

Alibaba announced Qwen3.8-Flash-Next: 125B total with only 6B active per token, plus 51B in N-gram embeddings and a redesigned sparse attention. What Qwen has confirmed, what's still community estimate, how much memory it really needs, and why the architecture is being published ahead of Qwen 4. No official benchmark has come out so far.

Alibaba shipped Qwen 3.8 27B and someone opened the diff against 3.6: 59 of 59 graph nodes map one-to-one, and the only differing field is metadata. Same architecture, DeepSWE tripling from 13.3 to 42.2. Here are the real benchmarks (and what the vendor table leaves out), the VRAM math the press oversimplified, the 64KB-per-token KV cache, the Jinja template bug that kills tool calls on day 1, and the difference between the dense 27B and the 2.4T 3.8 Max. With the counterpoint nobody made.

Alibaba is publishing the weights of Qwen3.8-Max, 2.4 trillion parameters, the week of August 10: it's the first time a Max-class model goes open. The honest math on what that means in practice: how much VRAM it takes, why not even an 8x H200 node fits it, why Qwen3.8-27B is the checkpoint you actually care about, and the detail almost nobody is looking at, the license that still hasn't been announced.