Qwen3.8-Flash-Next vs Qwen 3.5 122B-A10B (MoE)
Side-by-side VRAM requirements, benchmark scores, and GPU compatibility for local AI inference.
Quick verdict
Qwen 3.5 122B-A10B (MoE) is more hardware-efficient: it needs 83.4 GB at its Q4_K_M build vs 123.0 GB for Qwen3.8-Flash-Next's Q4_K_M, fitting on 33 GPUs natively.
Analysis
Qwen 3.5 122B-A10B and Qwen3.8-Flash-Next are six months apart from the same team, and underneath the size difference they share an unusual amount of skeleton: both are 48-layer hybrid MoE stacks built from twelve repeats of three Gated DeltaNet layers followed by one full-attention-family layer, and both cache with the identical 2 KV heads by 256 head dim. The only thing that changed in that one-in-four slot is what kind of layer sits there: Qwen 3.5 122B-A10B uses plain Gated Attention, Qwen3.8-Flash-Next replaces it with the newer Qwen Sparse Attention (QSA).
Because the caching layer count, ratio, and width are identical, the two models' KV cache scales as exactly the same function of context length, byte for byte, despite one being a six-months-newer preview architecture and the other a shipped production release. What differs is everything upstream of that cache: Qwen3.8-Flash-Next routes through 512 experts (10 routed plus 1 shared) against Qwen 3.5 122B-A10B's 256 (8 routed plus 1 shared), and activates fewer parameters per token doing it, 6B against 10B, while carrying nearly 50% more total parameters, 180B against 122B. Most of that extra mass isn't backbone at all: Qwen3.8-Flash-Next's real 180B total includes a 51B-parameter n-gram embedding table its own technical report says is meant to run from host RAM, not VRAM, a wrinkle Qwen 3.5 122B-A10B's conventional weight file doesn't have. On the two benchmark fields both report, the newer model leads clearly despite activating little more than half the parameters: GPQA Diamond 91.7 against 86.6, and LiveCodeBench v6 91.9 against 78.9. Qwen 3.5 122B-A10B answers back with everything Qwen3.8-Flash-Next doesn't have yet: real community GGUF quants, an Ollama tag, and the simpler Apache 2.0 license, against Qwen3.8-Flash-Next's Community 1.0 terms, which require a separate license for any Model-as-a-Service or 'AI Work Assistant' business built on it. Both accept text, image, and video input.
Bottom line: Qwen 3.5 122B-A10B is the model to actually run today: it fits an 80GB card at its recommended Q3_K_M, has a real quant ladder and Ollama support, and scores respectably on the benchmarks both share. Qwen3.8-Flash-Next scores higher on those same benchmarks at less than half the active compute, but it is explicitly a preview of Qwen4's likely architecture, needs a 141GB-or-larger card at its own recommended Q4_K_M (vLLM and SGLang can offload the 51B n-gram table to host RAM instead, which lowers that bar, but neither a GGUF build nor a confirmed community quant exists yet). Pick Qwen3.8-Flash-Next to see where Qwen's hybrid-MoE recipe is headed next; pick Qwen 3.5 122B-A10B if you actually need to load something this week.
Total vs. active parameters: more capacity, less compute
Both models are MoE, so total parameters (what has to fit in VRAM) and active parameters (what actually computes per token) move independently. Qwen3.8-Flash-Next carries the larger total but activates fewer parameters per token than its smaller predecessor.
The same KV-cache math, six months and one architecture apart
Both models cache with the exact same 12-of-48 layer ratio at the exact same 2-KV-head, 256-dim width, so their KV cache grows as literally the same line with context, the cleanest case this site tracks of two different-generation models sharing identical cache scaling. Whatever separates them at long context comes entirely from the weights, not the cache.
KV cache only, at FP16. Weights and activation overhead sit on top of these figures.
At the full 262,144-token native window both models share, each needs exactly 6.4 GB of KV cache, the same figure for both. Add each model's Q4_K_M weights and the full picture is 130.0 GB total for Qwen3.8-Flash-Next against 90.4 GB for Qwen 3.5 122B-A10B, a gap that is entirely the newer model's larger weight file, mostly its 51B-parameter n-gram table, not anything about how either model handles context.
VRAM at each quantization (8k context)
| Quant | Qwen3.8-Flash-Next | Qwen 3.5 122B-A10B (MoE) | Diff |
|---|---|---|---|
| FP32 | 806.6 GB | 546.8 GB | +48% |
| BF16 | 403.4 GB | 273.5 GB | +48% |
| FP16 | 403.4 GB | 273.5 GB | +48% |
| Q8_0 | 214.5 GB | 145.5 GB | +47% |
| Q6_K | 165.7 GB | 112.4 GB | +47% |
| Q5_K_M | 143.8 GB | 97.5 GB | +47% |
| Q4_K_M | 123.0 GB | 83.4 GB | +47% |
| Q3_K_M | 97.2 GB | 66.0 GB | +47% |
| Q2_K | 77.0 GB | 52.3 GB | +47% |
| NVFP4 | 101.0 GB | 68.5 GB | +47% |
Diff is Qwen3.8-Flash-Next relative to Qwen 3.5 122B-A10B (MoE). Green = lower VRAM (fits more GPUs).
Model specifications
| Spec | Qwen3.8-Flash-Next | Qwen 3.5 122B-A10B (MoE) |
|---|---|---|
| Org | Alibaba | Alibaba |
| Parameters | 180B | 122B |
| Architecture | MoE (6B active) | MoE (10B active) |
| Context | 256k tokens | 256k tokens |
| Modalities | text, vision, video | text, vision, video |
| License | Qwen Community 1.0 | Apache 2.0 |
| Commercial | Yes | Yes |
| Released | 2026-08-26 | 2026-02-15 |
| GPUs (native) | 22 / 119 | 33 / 119 |
Benchmark scores
| Benchmark | Qwen3.8-Flash-Next | Qwen 3.5 122B-A10B (MoE) |
|---|---|---|
| GPQA Diamond | 91.7 | 86.6 |
| LiveCodeBench | 91.9 | 78.9 |
| SWE-bench Pro | 62.5 | N/A |
Green = higher score (better). N/A = not yet available. ~ = inherited from a base model, not independently reported for that release itself.
GPUs that run only Qwen3.8-Flash-Next(0)
Every GPU that runs Qwen3.8-Flash-Next also runs Qwen 3.5 122B-A10B (MoE).
GPUs that run only Qwen 3.5 122B-A10B (MoE)(11)
- NVIDIA H100 80GB80 GB
- NVIDIA A100 80GB80 GB
- AMD Strix Halo (64GB)64 GB
- Apple M5 Max (64GB)64 GB
- Apple M5 Pro (64GB)64 GB
- Apple M4 Max (64GB)64 GB
- Apple M3 Max (64GB)64 GB
- Apple M2 Ultra (64GB)64 GB
- Apple M2 Max (64GB)64 GB
- Apple M1 Ultra (64GB)64 GB
- +1 more
GPUs that run both natively(22)
- NVIDIA B300 288GB288 GB
- NVIDIA B200 180GB180 GB
- NVIDIA H200 141GB141 GB
- NVIDIA RTX Pro 600096 GB
- NVIDIA DGX Spark (128GB)128 GB
- AMD Instinct MI300X192 GB
- AMD Strix Halo (128GB)128 GB
- AMD Strix Halo (96GB)96 GB
- Apple M5 Ultra (512GB)512 GB
- Apple M5 Ultra (256GB)256 GB
- Apple M5 Ultra (96GB)96 GB
- Apple M5 Max (128GB)128 GB
- +10 more GPUs run both
Which should you use?
- • You want maximum capability and have a 123 GB+ GPU
- • You're running coding tasks
- • It's the newer release (2026-08-26 vs 2026-02-15); check the benchmark table above for what actually improved
- • You have limited VRAM: it's a smaller model needing 83.4 GB vs 123.0 GB
Frequently asked questions
- Which is better, Qwen3.8-Flash-Next or Qwen 3.5 122B-A10B (MoE)?
- Qwen3.8-Flash-Next has 180B parameters vs 122B for Qwen 3.5 122B-A10B (MoE), so Qwen3.8-Flash-Next is the larger model. Qwen 3.5 122B-A10B (MoE) is more hardware-efficient, needing 83.4 GB at its Q4_K_M build vs 123.0 GB for Qwen3.8-Flash-Next's Q4_K_M. Qwen 3.5 122B-A10B (MoE) runs on more GPUs natively (33 vs 22).
- How much VRAM does Qwen3.8-Flash-Next need vs Qwen 3.5 122B-A10B (MoE)?
- At 8k context, Qwen3.8-Flash-Next needs approximately 123.0 GB of VRAM at its Q4_K_M build, while Qwen 3.5 122B-A10B (MoE) needs 83.4 GB at its Q4_K_M build. At the largest build each ships, Qwen3.8-Flash-Next requires 403.4 GB (FP16) vs 273.5 GB (FP16) for Qwen 3.5 122B-A10B (MoE).
- Can you run Qwen3.8-Flash-Next on the same GPUs as Qwen 3.5 122B-A10B (MoE)?
- Yes, 22 GPUs can run both natively in VRAM, including NVIDIA B300 288GB, NVIDIA B200 180GB, NVIDIA H200 141GB. However, no GPU can run Qwen3.8-Flash-Next without also fitting Qwen 3.5 122B-A10B (MoE), and 11 GPUs can run Qwen 3.5 122B-A10B (MoE) but not Qwen3.8-Flash-Next.
- What is the difference between Qwen3.8-Flash-Next and Qwen 3.5 122B-A10B (MoE)?
- Qwen3.8-Flash-Next has 180B parameters (6B active, MoE) with a 256k context window. Qwen 3.5 122B-A10B (MoE) has 122B parameters (10B active, MoE) with a 256k context window. Licensing differs: Qwen3.8-Flash-Next is Qwen Community 1.0 while Qwen 3.5 122B-A10B (MoE) is Apache 2.0.
- Which model fits in 24 GB of VRAM, Qwen3.8-Flash-Next or Qwen 3.5 122B-A10B (MoE)?
- Neither fits in 24 GB: Qwen3.8-Flash-Next needs 123.0 GB at Q4_K_M and Qwen 3.5 122B-A10B (MoE) needs 83.4 GB at Q4_K_M. Both require a multi-GPU server with 123 GB+ of combined VRAM.
- Which handles long context better, Qwen3.8-Flash-Next or Qwen 3.5 122B-A10B (MoE)?
- At the full 262,144-token native window both models share, each needs exactly 6.4 GB of KV cache, the same figure for both. Add each model's Q4_K_M weights and the full picture is 130.0 GB total for Qwen3.8-Flash-Next against 90.4 GB for Qwen 3.5 122B-A10B, a gap that is entirely the newer model's larger weight file, mostly its 51B-parameter n-gram table, not anything about how either model handles context.