Request for Qwen4-35B-A3B-Distill-FlashNext

#54
by userr99 - opened

Can you build roughly:

Qwen4-35B-A3B-Distill-FlashNext using:

32–48 layers
~2560–3072 hidden size
Qwen Sparse Attention
Gated DeltaNet hybrid
4-stream Gated Residual / Hyper-Connections
smaller PLE / n-gram memory
maybe 128–256 experts rather than Flash-Next’s 512
~6–12 routed experts/token
~3–4B active/token
same tokenizer as Flash-Next
Flash-Next itself as the teacher

That would preserve the architectural advantages instead of trying to cram Flash-Next behavior and assumes the precedent that the architecture really can run independently since it's already been implemented in llama.cpp-compatible and even standalone CPU runtimes, including Gated Residual, GDN, QSA, PLE and the MoE routing machinery.

A good, useful and strong model for the popular systems with 16GB of VRAM could be a 17-billion parameter dense model using n-grams. At the Q6/Q6XL quantization level (~12-15 GB), it fits within 16GB and the KV cache in this architecture it is compact enough to be offloaded to RAM. The n-grams would be stored on the SSD. In MoE models with many experts, the router faces significant pressure because there are too many combinations, without sufficient width and depth on a small MoE it will under-perform and stall the whole model.

Steam runs a community survey, and it turns out that 16GB VRAM is the most popular VRAM size in their user base, yet it seems to be skipped by Qwen3.8, neither 27B or Flash-Next works until you get down to inaccurate quants, or offload the important layers which kills the speed. There is no 9B dense variant to make up for it either.

Well we might have to wait for Qwen4 as 3.8 is just a preview, Qwen4 hopefully will have a 35B A3B, 9B etc... in my case i have RTX3060 12gb and a lot of ddr4 ram so for me 35 A3B is the nicest, with dflash i get around 60t/s with 131k context in lmstudio... :D and is pretty decent to work with via claudecode

Sign up or log in to comment