Welcome 👋
We're launching
@Alibaba_Qwen 3.8-Flash-Next on BOTH and today!
This is our first challenge on We see a lot of overlap between the MLX and CUDA communities, and we want to see how far both can push the same model. So we're putting their progress on the same graph for this one! Just some friendly neighborhood competition 😉
The challenge: make Qwen 3.8 Flash Next run faster on two concrete setups:
--- our Qwen port of
@antirez's ds4 C/CUDA engine with
@UnslothAI's Qwen3.8-Flash-Next-GGUF on 1x NVIDIA DGX Spark.
--- our Qwen Swift/Metal engine, built on the MLX and mlx-swift-lm forks, on 1x M5 128 GB MacBook.
Both tracks measure one response stream at a time. Your changes must pass the correctness checks, then beat the reference engine on the same machine. The score combines faster prompt processing (prefill) and token generation (decode), weighted 25% and 75% in the geometric mean.
We chose Qwen 3.8 Flash Next because it beats Claude Opus 4.6 Max reasoning on 94% of the benchmarks from Qwen's published comparison. That's 15 out of 16, spanning coding, reasoning, instruction following, and vision! Also this model can be ran on a single Spark or a 128 GB MacBook. That's what makes this worth pushing: every inference improvement makes that capability more useful on developer hardware.
Our current starting decode rates are around 17–18 tokens/sec on the Spark and 35–36 tokens/sec on the Mac. Let's see how far we can push both!
Thank you to
@TheDavidTai and
@GumbiiDigital for building the entire challenge (it was not easy!),
@antirez @ivanfioravanti & many others for their ds4 work (the Gs), and the MLX and Qwen teams for the work we're building on.
One caveat: this is a significantly larger model, so local testing will be harder for some smaller Macs. We recommend a DGX Spark or a Mac with more than 128 GB of memory to give yourself room to work.