r/Qwen_AI • u/tiguidoio • Aug 14 '26
r/Qwen_AI • u/GapNew4766 • 6d ago
Benchmark Qwen 3.8 27B wrote 2,860 lines and made Fable 5.2 5x cheaper and 2x faster
2,860 lines of JS and HTML, all written by Qwen 3.8 27B on a MacBook. Three copies of it built a 3D pop-up book film in 11 minutes, and the only cloud cost was $2.98 for Fable 5.2 giving orders.
| Who writes the code | Time | Cloud bill |
|---|---|---|
| 3 local Qwen 3.8 27B builders, Fable 5.2 as the boss | 11:32 | $2.98 |
| Fable 5.2 alone | 21:27 | $15.77 |
The prompt was a 30-second film in Three.js: a paper book opens and four worlds fold out of it, a castle, a jungle, a port and snowy peaks. Fable never touched a file in the orchestration run. It planned and reviewed, and Qwen did all of the writing.
How Qwen did as a builder:
The first round was rough. Out of 8 tasks, 5 finished, 1 timed out, 1 ran out of steps and 1 went back to the boss.
The second round was clean. Once the boss narrowed the briefs, Qwen went 5 for 5.
Failing locally costs nothing. Every retry ran on the laptop, so the bad round didn't add to the cloud bill the way it would with a cloud model writing the code.
Three at once was the speed. One local builder is slower than Fable, but three writing in parallel finished in about half the time.
Setup: MacBook Pro M5 Max 64 GB, Qwen 3.8 27B Q4_K_XL, llama.cpp, 196K context across three parallel slots, reasoning off, orchestration in Atomic Agent 0.6.13. One run per setup, so it's a data point and not a benchmark.
How is 27B holding up as a coding builder for you? Has anyone pushed it past three parallel slots?
Disclosure: I work on Atomic Agent, the open source agent this ran in, so ask me anything!
r/Qwen_AI • u/koc_Z3 • Jul 24 '26
Lets Chill... CTO of hugging face ran Qwen 27B locally on the plane
This is old stuff, but it would be a good experience to try 27B locally on a plane
r/Qwen_AI • u/AmbassadorOk934 • 25d ago
News Qwen 4 news
Qwen 4 will be released on the end month and will be releasing in November and other months. So, we can wait it soon. It is releasing.
Resources: https://x.com/luminabench/status/2113217029675085963?s=46
Discuss what do you think about its level. I waiting for qwen plus and small models.
KIMI K3.1 too releasing, for me its paid so qwen is winner for that. Deepseek situation: Dont know
r/Qwen_AI • u/JLeonsarmiento • Jul 19 '26
Funny Dear Qwen sir, can we have 3.8-35B-a3b, please sir? 🙏
r/Qwen_AI • u/SchemeBetter454 • Sep 11 '26
News Canadian company claims its harness lifts Qwen3.8-27B to outperform Fable 5. Releases the harness for free.

Canadian company claims its harness lifts Qwen3.8-27B to outperform Fable 5. Releases the harness for free.
r/Qwen_AI
•
u/koc_Z3
•
Mar 28 '26
Other LLM Bruner coming soon? Burn Qwen directly into a chip, processing 10,000 tokens/s
The “Medium-sized” LLM Burner is coming soon, this could make local HyperToken generation a reality.
Application-specific hardware — Taala’s new PCIe ASIC card will burn an entire medium-sized Qwen 3.5-27B LLM directly into silicon.
Taalos says that by Spring 2026, their lab will offer ASIC-based medium-sized models. No more added weights.
~10,000 tokens per second processed locally (Llama 3.1 8B already hits 17,000 tokens/sec)
Standard PC slot, ultra-low power consumption (10x less), no gpu farm
Reddit rumors put the unit price at $300–$400
r/Qwen_AI
•
u/KnownAd4832
•
Sep 27 '26
Benchmark Qwen3.8-Flash-Next on 12GB VRAM - 65 t/s
Qwen3.8-Flash-Next on 12GB VRAM - 65 tokens per second
a while ago I posted 15 tok/s output and 100-120 tok/s prompt processing with the IQ3_XXS quant on a 12GB RTX 5070 using llama.cpp. Since then I built my own inference engine for this one model and this kind of PC. The same IQ3_XXS now runs at ~65 tok/s output and ~430 tok/s prompt processing, and the 2-bit quants run faster still using RCO-GSQ quantization.
Using:
64GB DDR5 (5600)
12GB RTX 5070 SFF (Gigabyte)
Ryzen 5 7600 CPU
Windows
Output (tokens/s) on 128K context:
Q2_0 (equivalent to unsloth Q3): 65
IQ2_XS (equivalent to unsloth Q4): 52
IQ3_XXS (equivalent to unsloth Q5): 45
IQ3_S (equivalent to BF16 supposedly): 42
Prompt processing (tokens/s) on 128K:
Q2_0: 539
IQ2_XS: 463
IQ3_XXS: 410
IQ3_S: 374
Requirements:
Q2_0 = 37.6GB minimum in RAM+VRAM
IQ2_XS = 39.2GB minimum in RAM+VRAM
IQ3_XXS = 47GB minimum in RAM+VRAM
IQ3_S = 54.8GB minimum in RAM+VRAM
Vision encoder = 0.91GB additionally
You can now one click install and run the engine with low cost hardware (currently only optimized for CUDA-NVIDIA).
Supported Models:
Qwen3.8-Flash-Next-GSQ-RCO
Swift1.5-Qwen3.8-Flash-Next-GSQ-RCO
r/Qwen_AI
•
u/ryanmerket
•
13d ago
News NEW: GPT-6 Astra edited 0.016% of Qwen's weights and its math score went up 6x
r/Qwen_AI • u/suspicious_bread3842 • 8d ago
Funny Qwhy?
I thought it was supposed to release last week? It better be monumental, i know we're all waiting for Qwen 4 27b
r/Qwen_AI
•
u/Aggressive_Basket798
•
5d ago
Model Finally it come, me so exciting to try the new Qwen models
r/Qwen_AI • u/No_Ideal8394 • Sep 26 '26
Model OMG !!! Just cracked a software
Paying €10/year per PC for an IDM license key?
Nope.
Paying €5 for a cloud GPU to throw Qwen 3.8 at the problem?
Absolutely. 😂
I honestly wasn't expecting much, but I was genuinely blown away by what it could do.
I basically described what I wanted, gave it roughly 250k tokens of context and about 30 minutes later, it had figured out a working patch.
No hand-holding. No step-by-step guidance. Just: “Here’s what I want. Make it happen.”
And honestly…
I don't even want to imagine what the frontier models are going to be capable of. 💀
r/Qwen_AI • u/TheRealSol4ra • 24d ago
Image Gen Qwen Image 2.1 Is Nuts
Qwen Image 2.1 Base + Anything2Real, TheseAlpacas v2 and Consistency LoRAs
r/Qwen_AI • u/Tiny-Assumption4263 • Aug 14 '26
Experiment Qwen 3.8 27b is just unreal, real coding test inside.
TL;DL: Gave Qwen 3.8 27b a simple prompt and it build this: https://qwen3-8-eccomerce-test.vercel.app/
Repo: https://github.com/catriel25/qwen3.8-eccomerce-test
Like everybody else in the local AI community today, I dowloaded Qwen 3.8 27b UD-Q4_K_XL as soon as it was published.
I'm running it in a single rtx 3090, no mtp, 110k context and kv cache f16 with llama.cpp, same flags used with Qwen 3.6 27B.
I have this stupid test that I run with every new model that comes out. It consist in connecting the model to pi code (almost vanilla, only internet access and some simple navigation tools I built) and giving it this prompt:
"Construye el frontend completo de un pequeño ecommerce premium para una panadería artesanal usando Next.js App Router (JavaScript).
El proyecto debe ser frontend-only en esta etapa. No debe incluir backend, base de datos, autenticación ni pasarelas de pago. El checkout debe finalizar redirigiendo a WhatsApp con un mensaje de pedido bien estructurado.
La app debe incluir una experiencia completa de compra: home, catálogo con productos de panadería, categorías, productos destacados, carrito, resumen de pedido y checkout. Usá mock data local para productos, categorías, precios, descripciones, disponibilidad e imágenes o placeholders visuales. Todo debe quedar preparado para conectar posteriormente un backend real sin tener que rehacer la arquitectura principal del frontend.
El diseño debe sentirse extremadamente premium, artesanal, moderno y cuidado. No quiero una landing genérica ni una interfaz básica. La primera pantalla debe comunicar claramente la identidad de la panadería, mostrar producto real o visualmente convincente, y permitir empezar a comprar. La experiencia debe ser excelente tanto en desktop como en mobile.
El catálogo debe permitir explorar productos, ver información clara de cada ítem y agregarlos al carrito. El carrito debe permitir modificar cantidades, eliminar productos y ver totales. El checkout debe pedir datos mínimos necesarios para el pedido, permitir notas o preferencias, y generar una URL de WhatsApp con productos, cantidades, subtotales, total y datos del cliente.
La estructura del código debe separar razonablemente datos mock, tipos de dominio, utilidades de checkout/WhatsApp, componentes de catálogo, componentes de carrito y vistas principales. La solución debe quedar lista para reemplazar la mock data por datos de backend en una etapa posterior."
Those are just instructions to build a nextjs project (javascript only) with the frontend for small eccomerce with whatsapp checkout, leaving everthing ready to connect a backend later. Nothing else, no skills, no more feedback. Just one prompt and watching the result.
I have run this test with all the models and finetunes I can fit in my GPU, and not a single one was even close to this result.
Not a single alert form nextjs (wich was usual before) or something that looks broken.
At some point, this bastard realised it didn't had visión (lol, not enough VRAM buddy) and it decided FUCK IT, I'M GONNA BUILD THE IMAGES MYSELF. He made SVGs for every product card.
I have more testing to do like trying it in a real codebase but... I can't believe i'm running this thing in a single RTX 3090, it is just unreal.
Imagine 2 years from now.
Biggest fuck you Dario of the year.
r/Qwen_AI
•
u/Imaginary-Anywhere23
•
Mar 30 '26
Model TurboQuant isn’t just for KV: Qwen3.5-27B at near-Q4_0 quality, about 10% smaller, and finally fitting on my 16GB 5060 Ti
Hugging Face GGUF: YTan2000/Qwen3.5-27B-TQ3_1S
I bought an RTX 5060 Ti 16GB around Christmas and had one goal: get a strong model running locally on my card without paying api fees. I have been testing local ai with open claw.
I did not come into this with a quantization background. I only learned about llama, lmstudio and ollama two months ago.
I just wanted something better than the usual Q3-class compromise (see my first post for benchmark). Many times, I like to buy 24gb card but looking at the price, I quickly turned away.
When the TurboQuant paper came out, and when some shows memory can be saved in KV, I started wondering whether the same style of idea could help on weights, not just KV/ cache.
P/S. I was nearly got the KV done with cuda support but someone beat me on it.
After many long nights (until 2am) after work, that turned into a llama.cpp fork with a 3.5-bit weight format I’m calling TQ3_1S:
Walsh-Hadamard rotation
8-centroid quantization
dual half-block scales
CUDA runtime support in
llama.cpp
This work is inspired by the broader transform-based quantization line, especially RaBitQ-style Walsh-Hadamard rotation ideas and the recent TurboQuant result (Tom). The thing I wanted to test was whether that same geometry could help on weights, not just KV/cache.
Main Result on Qwen3.5-27B
Q4_0:7.2431 +/- 0.04822TQ3_1S:7.2570 +/- 0.04802
That is a gap of only +0.0139 PPL, about 0.19%, on the full wiki.test.raw pass (580 chunks, c=512).
Size
Q4_0: about14.4 GBTQ3_1S: about12.9 GB
So TQ3_1S is about 10% smaller while staying near Q4_0 quality.
The practical point for me is simple:
TQ3_1Sfits fully on my 16GB RTX 5060 TiQ4_0does not fit fully on GPU in the same setup
So I’m not claiming “better than Q4_0” in general. I’m claiming something narrower and, I think, useful:
near-
Q4_0qualitymaterially smaller than
Q4_0enough to make a 27B model practical on a 16GB card
Speed record during perplexity test:
- prompt processing pp512: 130.87 tok/s
- generation tg10: 15.55 tok/s
Caveats
this is the strongest result on the 27B witness, not a blanket claim that plain TQ3 works equally well on every model size
I am pretty new to this, so I may miss a lot of test. I only have one card to test :-)
Be skeptical as I can't believe I publish my own model
the speed story here is mainly a deployment/fit win on this GPU class, not a blanket claim that native TQ3 kernels are always faster than native
Q4_0
Links
GitHub fork: turbo-tan/llama.cpp-tq3
Hugging Face GGUF: YTan2000/Qwen3.5-27B-TQ3_1S
I will open source the quantization steps when I have enough feedback and test.
Update: Since a few saying I only compare to q4_0. Here is update. TQ3_4S will be published with faster processing speed
| Format | bpw | PPL (c=2048) | Size |
|---|---|---|---|
| TQ3_4S | 4.00 | 6.7727 | 12.9 GB |
| Q3_K_S | 3.44 | 6.7970 | 11.4 GB |
| IQ4_XS | 4.25 | 6.8334 | 13.9 GB |
| TQ3_1S | 4.00 | 6.9186 | 12.9 GB |
| UD-Q2_K_XL | 3.30 | 7.5294 | 11.0 GB |
Updated: new model
TQ3_4S 2x speed, better quality
Turbo Quant in action (Latest Update)
10/Apr/2026 - Prompt processing nearly doubled to 708 tok/s
https://x.com/coffeecup2020/status/2042719160950456497?s=20
r/Qwen_AI • u/Intelligent-Taste-36 • Aug 03 '26
LLM I have to be honest and give double praise to Qwen's attitude. The open weights are coming and we will have The 27B version too!
First, I need to say that Qwen 3.8 Max Preview, in my opinion, is better than GPT 5.6 Terra and Luna, and perhaps even better than GPT 5.6 Sol.
It's fast, intelligent, and follows plans with high-quality development.
In addition to all that, it's open weights!
I prefer to support companies that disclose the weight of their LLMs.
The second reason why Qwen deserves applause is: Qwen 3.8 27B will be released!
This company will have my financial support by using their paid products, since they allow me to use their models on my hardware.
Learn how it's done, Anthropic.
r/Qwen_AI • u/druggedJordan • 9d ago
News QWEN 4 Preview IS INSANE! First Look at Qwen 4 Max & 27B! Greatest Open Model Ever!
r/Qwen_AI • u/After_Canary6047 • Oct 03 '26
Discussion Orca 3.8 Flash Next Insanity
Without getting into details, the Orca 3.8 Flash Next uncensored version is insane. I was literally in complete shock as I watched the responses while playing with it a bit today.
Honestly terrified, and that’s an understatement. Can’t imagine what will happen if bad actors have access to this.
This thing is both extremely intelligent and scored a 100/100 on complicated legal matters, with no MCP or RAG attached to it.
Whats even crazier is that you can run the 180B version with as little as 12GB of VRAM on account of this project, which I have nothing to do with.
https://github.com/Niko1221/Strata
Using the Orca version, it pulls about 75-80TPS output on a 4090. That being said, my daily 3.6 35B censored model pulls about 180TPS using Llama.cpp, though hey, I’ll take the slowdown for a bit of shock and awe any day, lol.
Enjoy responsibly boys and girls! 😜
r/Qwen_AI • u/2fit2fitin • Aug 06 '26
Benchmark After updated score, Qwen 3.8 now frontier on agentic benchmark
i will say my own use differs from this. For me GPT Sol seems the best but all past Kimi K3 produce similar result.
But I will say my use it not very intensive. Maybe some of y’all working on solving the Riemann hypothesis can find the differences at the frontier
r/Qwen_AI • u/Secure_Recording_472 • Sep 11 '26
Discussion Qwen 3.8 27B overthinks a lot so I fixed it (TB 2.1, LiveCodeBench v6 included)
EDIT 3: Added Q4,Q5,Q6,Q8 on the GGUF! https://huggingface.co/ukisai/Swift-Qwen3.8-27B-GGUF
EDIT 2: Added a free API so people test it before spending time! https://ukisai.com/api/swift/v1
EDIT: I think I didn't explain it properly: 1. it's based on this paper by meta https://arxiv.org/abs/2606.00206 and was initially made for quantized models and tackled "overthinking errors" directly (the random loops an int4 model can get that come from PTQ), but it turns out it has a much wider application! 2. i explicitly ran so many benchmarks (and all x5!) to make sure i'm not giving out slop to people 3. i also tried reasoning effort low / medium / no thinking but they all took a huge accuracy drop so i had to come up with a way to keep it so my coding agent actually works, this was basically the only way i found
Hi guys
Everybody (me included) was complaining about Qwen 3.8 27B using too much tokens and being too slow so I analysed what tokens are linked to the overthinking and penalized them via finetuning and got a model that thinks 58.3% less and lost <1% accuracy across 10 benchmarks
Swift-27B vs Qwen3.8-27B (BF16, all benchmarks ran x5)
LiveCodeBench v6: 76.8% → 81.6% (+4.8pp), 46% fewer median thinking tokens
Terminal-Bench 2.1: 66.7% → 65.8%, 39% fewer median tokens
GPQA-Diamond: 88.4% → 88.3%, 58% fewer median tokens
IFBench: 73.5% → 71.8%, 51% fewer median tokens
ERQA (vision): 67.5% → 66.3%, 51% fewer mean tokens
https://huggingface.co/ukisai/Swift-Qwen3.8-27B
I also included a lot about the training, exact benchmark configs etc
Let me know if it's useful, i'm trying to get the quants out as soon as I have compute
r/Qwen_AI
•
u/gladkos
•
May 21 '26
Experiment Qwen 3.7-max beats Opus 4.7 and GPT-5.5
We tested three frontier models on a real agentic task: write a Tetris bot that plays the game and trains itself. Each model could read its own code, run benchmarks, and rewrite itself across 10 iterations. Then we compared the final bots head to head.
Qwen 3.7-Max: training cost $1.32, bot improvement +56%
Claude Opus 4.7: training cost $12.15, bot improvement +28%
GPT-5.5: training cost $2.85, bot improvement +7%
Qwen won on every dimension - biggest jump, 9× cheaper than Claude, 2× cheaper than GPT. Long agentic loops is where Qwen Max actually delivers.
Open source Local Ai app: Atomic.Chat
