I wish that all announcements of models would show what (consumer) hardware you can run this on today, costs and tok/s.
Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
31–40 of 482 posts
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#32I wish that all announcements of models would show what (consumer) hardware you can run this on today, costs and tok/s.
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#33Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#34Good news! Friendly reminder: wait a couple weeks to judge the ”final” quality of these free models. Many of them suffer from hidden bugs when connected to an inference backend or bad configs that slow them down. The dev community usually takes a week or two to find the most glaring issues. Some of them may require patches to tools like llama.cpp, and some require users to avoid specific default options. Gemma 4 had…
The bugs come from the downstream implementations and quantizations (which inherit bugs in the tools).
Expect to update your tools and redownload the quants multiple times over 2-4 weeks. There is a mad rush to be first to release quants and first to submit PRs to the popular tools, but the output is often not tested much before uploading.
If you experiment with these on launch week, you are the tester. :)
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#35Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#36I wish that all announcements of models would show what (consumer) hardware you can run this on today, costs and tok/s.
As this is a dense model and it's pretty sizable, 4-bit quantization can be nearly lossless. With that, you can run this on a 3090/4090/5090. You can probably even go FP8 with 5090 (though there will be tradeoffs). Probably ~70 tok/s on a 5090 and roughly half that on a 4090/3090. With speculative decoding, you can get even faster (2-3x I'd say). Pretty amazing what you can get locally.
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#37Good news! Friendly reminder: wait a couple weeks to judge the ”final” quality of these free models. Many of them suffer from hidden bugs when connected to an inference backend or bad configs that slow them down. The dev community usually takes a week or two to find the most glaring issues. Some of them may require patches to tools like llama.cpp, and some require users to avoid specific default options. Gemma 4 had…
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#38Generate an SVG of a dragon eating a hotdog while driving a car: https://codepen.io/chdskndyq11546/pen/xbENmgK
Far from perfect, but it really shows how powerful these models can get
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#39I wish that all announcements of models would show what (consumer) hardware you can run this on today, costs and tok/s.
TLDR: If you have 14GB of VRAM, you can try out this model with a 4-bit quant.
Tokens per second is an unreasonable ask since every card is different, are you using GGUF or not, CUDA or ROCm or Vulkan or MLX, what optimizations are in your version of your inference software, flags are you running, etc.
Note that it's a dense model (the Qwen models have another value at the end of the MoE model names, e.g. A3B) so it will not run very well in RAM, whereas with a MoE model, you can spill over into RAM if you don't have enough VRAM, and still have reasonable performance.
Using these models requires some technical know-how, and there's no getting around that.
Re: Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model
#40A bit skeptical about a 27B model comparable to opus...
Every release is accompanied by claims of being as good as Sonnet or Opus, but when I try them (even hosted full weights) they’re far from it.
Impressive for the size, though!