--- title: Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU... description: Alibaba released Qwen3.8-27B on Hugging Face under Apache 2.0, a dense variant of its 2.4T flagship model that fits on a single GPU regardless of precision... canonical: https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU with 262K context | daily.dev og:description: Alibaba released Qwen3.8-27B on Hugging Face under Apache 2.0, a dense variant of its 2.4T flagship model that fits on a single GPU regardless of precision... og:url: https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc og:image: https://api.daily.dev/og/posts/Mzhf0NYjc.png og:image:alt: Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU with 262K context og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU with 262K context **[Collections](https://daily.dev/sources/collections)** · 1 min read · 1 upvotes · 0 comments ## Summary Alibaba released Qwen3.8-27B on Hugging Face under Apache 2.0, a dense variant of its 2.4T flagship model that fits on a single GPU regardless of precision (BF16, FP8, or an NVFP4 build from Inferact). It offers a native 262K context window extendable to 1M via YaRN, and ships with a built-in MTP draft head enabling out-of-the-box speculative decoding, with acceptance rates of 92.2% (BF16) and 84.8% (FP8) on short prompts. vLLM verified end-to-end operation on NVIDIA GB300 hardware, including tool calls and full 1M context generations, requiring vLLM nightly and transformers 5.8.0+. Early benchmark claims suggest performance on par with Opus 4.6, though independent verification is still pending. ## Content Alibaba just released Qwen3.8-27B, and the local-AI crowd has basically not shut up about it since. It's a 27-billion-parameter, open-weight, native multimodal dense model, licensed under Apache 2.0, and it's genuinely one of the more interesting model drops I've seen in a while — not because it's the biggest or smartest thing out there, but because of *where* it runs. ## The pitch: frontier-ish intelligence on a laptop On Artificial Analysis's Intelligence Index, Qwen3.8-27B lands close to cloud heavyweights like GPT-5.6 and Claude Opus 4.6. On benchmarks people actually care about for coding and agent work, it's downright uncomfortable for the closed-source labs: SWE-bench Pro 61.7 vs Opus's 53.4, CoWorkBench 70.7 vs 68.2, OSWorld 84.3 vs 72.7. GPQA is close too (89.2 vs 91.3). One tweet summed up the reaction pretty well: this thing ## Questions this post answers ### What are the benchmark scores for Qwen3.8-27B compared to Claude Opus 4.6? Qwen3.8-27B scores higher than Claude Opus 4.6 on several coding and agent benchmarks: SWE-bench Pro 61.7 vs 53.4, CoWorkBench 70.7 vs 68.2, and OSWorld 84.3 vs 72.7. On GPQA it trails slightly, scoring 89.2 versus Opus's 91.3, placing it close to frontier closed-source models overall. _Developers weighing open-weight versus closed models for coding agents can track releases like this on daily.dev._ ### Can Qwen3.8-27B run on a single consumer GPU? Yes, Qwen3.8-27B is a 27-billion-parameter dense model designed to run on a single GPU while supporting a 262K token context window. It is released as an open-weight model under the Apache 2.0 license, making it usable for local inference without relying on a hosted API from a closed-source provider. _Anyone planning local-first AI setups can follow open-weight model drops like this via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 691 comments across hackernews, lobsters (as of 2026-09-13). **TL;DR:** Developers are impressed that a 17-27GB local model can deliver this level of capability on consumer-ish hardware, but many report frustration getting good speeds without a beefy GPU/high memory bandwidth, and the default overthinking behavior is seen as a real usability flaw. **Sentiment:** 45% positive · 40% mixed · 15% skeptical **The case for** - Running a capable model locally on a laptop or modest GPU feels like a genuine milestone in local AI progress. - Several people report usable speeds (25-100 tok/s) on Macs or mid-range GPUs when the model fits in VRAM. - Some praise the model's vision/bounding-box and motion-graphics capabilities as genuinely impressive. **The pushback** - Performance falls off a cliff when the model doesn't fully fit in VRAM, making it impractical on many 'consumer' machines. - Memory bandwidth, not RAM capacity or raw compute, is repeatedly cited as the real bottleneck for local inference. - The default excessive reasoning effort ('xhigh') is called out as a broader pattern of frontier models overengineering simple tasks, wasting time and compute. - Users report confusing, inconsistent guidance on correct templates/settings across llama.cpp, Ollama, LM Studio, and quant variants, making optimal local setup hard to achieve. **By community** - hackernews (mixed): Enthusiasm about local model progress is tempered by extensive debate over hardware requirements, memory bandwidth bottlenecks, and a long tangential argument about whether LLMs pass the Turing test. - lobsters (mixed): No comments were provided for this discussion, so there isn't enough signal to characterize the community's take. **Hottest debate:** Whether memory bandwidth/VRAM capacity or compute power is the real bottleneck for running these models on consumer hardware. **Open questions** - Will a smaller or MoE variant (like a 3.8 MoE) be released to make the model more practical on limited hardware? - What is the actual mechanism behind the 'reasoning_effort' setting (deterministic API parameter vs. prompt engineering)? - How can users reliably determine the 'correct' template and inference settings for a given model across different runtimes? **Highlights** > “The fact that a 17GB file can do all of this stuff on my home machines is a miracle. Once again, I’m delighted and amazed at how much progress local models have made this year.” I think that should be the blinking headline - this shows what can be done with consumer hardware. > — [chvid on hackernews · 10 comments](https://news.ycombinator.com/item?id=49326409) > what??? not true! for inference the compute is the last thing we need more of. memory bandwidth is the numebr one blocker, after that the inefficiencies that where introduced with MoE models (and all new large models are made that way) Here is a quick read: https://news.ycombinator.com/item?id=49324600 > — [mhaberl on hackernews](https://news.ycombinator.com/item?id=49327590) > The other implication here is that this is all software improvements and optimization. There might be a lot more wiggle room for improving quality over time. It seems the model and reasoning quality is improving faster than the hardware currently. The over reasoning that Simon Willison highlights here is a real issue though. I've observed it with some of the OpenAI models as well. They are prone to overthinking and overengineering things. What I would love is models that figure out their own appropriate reasoning effort given a task. I'm spending too much brain cycles worrying on what model speed, reasoning, and quality settings to pick. It's not just a cost concern it's also a time concern. Wasting a lot of time for simple UI tweaks because the model is set to high or ultra or whatever is counter productive. The last few iterations of frontier models seem to emphasize benchmarks and reasoning effort. But of course the day to day reality of many developers is that they are trying to solve relatively simple problems compared to e.g. proving some so far unproven theorems, solving some Nobel prize level problems, etc. I'd love my tools to start making sane choices based on what I ask rather than defaulting to "boil the oceans". These tools need some kind of Auto select. Mostly Ultra is overkill and a waste of time and resources. And of course with local models, keeping simple things local is a nice option. It's nice to have Sol Ultra extra fast as an option in my back pocket. But it's complete overkill 99% of the time. And it's not like most users make good choices here or are even capable of making good, informed choices. The models are more intelligent than the tool UX. Arguably, a local model of very modest size might be able to do better for this specific choice. > — [jillesvangurp on hackernews](https://news.ycombinator.com/item?id=49328512) > For me that moment was Gemma 4 12B QAT. You're not suddenly going to start throwing your hardest programming problems at Gemma 4 12B QAT, it is still 15B parameters less. It's more that, aside from pelican art which isn't what local models are for, I didn't see anything on Simon's post that it couldn't assist with or largely succeed at. It can run 80-100t/s on a laptop, can understand images natively and do bounding boxes, read tiny text, understands audio natively as well and can transcribe or translate anything you say, can do accurate long context retrieval with pretty large context windows, tool calling, excellent reasoning and is very token efficient. It's only 7GB including the mmproj or 8GB with MTP. The Qwen 3.8 27B model Simon was using is ~18GB with MTP+mmproj, rather than 17GB alone. The point is not really that you compare these models directly, but that Gemma 4 12B QAT was really a special moment in model releases deserving of a similar reaction relative to its size, but was mutilated by Google themselves, Unsloth and Llama.cpp. The overall appreciation I think we're seeing this year in particular is that people are easily surprised when multiple things are improving simultaneously which produce seemingly exponential changes. It isn't just that models are getting smaller, or that reasoning is getting better, or that speculative decoding is becoming mainstream, or that models can understand audio and images better now, or that they can reliably call tools which expands their capabilities, or that context windows are getting larger, or that accurate retrieval is improved, or that.... and so on. It's all of them narrowing in at once that is starting to make local models incredible and truly useful for far more use cases on the existing hardware people already have. > — [CMay on hackernews · 4 comments](https://news.ycombinator.com/item?id=49327574) > Do these self hosted models avoid "protecting the user" or protecting big businesses? In other words can I just ask it any question and if it has the answer, I will get an answer rather than telling me it can't answer the question? I ask because Claude is fun for rewriting abandoned code and I am not a proper developer so it's been great for me. Claude refuses to answer questions about science and medicine that stray outside of the officially supported narratives of the AMA and I have issues that have surpassed anything a doctor can do so I am entirely on my own. Will the self hosted models answer such questions or will it also try to put walls or bumper guards around topics? > — [Bender on hackernews · 2 comments](https://news.ycombinator.com/item?id=49332406) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49324985) · 690 points · 688 comments - [lobsters](https://lobste.rs/s/k7myyp/qwen_3_8_27b_is_excellent_it_defaults) · 10 points · 3 comments --- Tags: [#machine-learning](https://daily.dev/tags/machine-learning), [#llm](https://daily.dev/tags/llm), [#ai-inference](https://daily.dev/tags/ai-inference), [#vllm](https://daily.dev/tags/vllm), [#qwen](https://daily.dev/tags/qwen) [View this post on daily.dev](https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU with 262K context","url":"https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc"},"datePublished":"2026-08-14T15:32:35.367Z","dateModified":"2026-09-13T19:47:00.006Z","description":"Alibaba released Qwen3.8-27B on Hugging Face under Apache 2.0, a dense variant of its 2.4T flagship model that fits on a single GPU regardless of precision...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"machine-learning,llm,ai-inference,vllm,qwen","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Qwen3.8-27B: Alibaba's dense 27B model runs on one GPU with 262K context"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/qwen3-8-27b-alibaba-s-dense-27b-model-runs-on-one-gpu-with-262k-context-mzhf0nyjc#faq","mainEntity":[{"@type":"Question","name":"What are the benchmark scores for Qwen3.8-27B compared to Claude Opus 4.6?","acceptedAnswer":{"@type":"Answer","text":"Qwen3.8-27B scores higher than Claude Opus 4.6 on several coding and agent benchmarks: SWE-bench Pro 61.7 vs 53.4, CoWorkBench 70.7 vs 68.2, and OSWorld 84.3 vs 72.7. On GPQA it trails slightly, scoring 89.2 versus Opus's 91.3, placing it close to frontier closed-source models overall. Developers weighing open-weight versus closed models for coding agents can track releases like this on daily.dev."}},{"@type":"Question","name":"Can Qwen3.8-27B run on a single consumer GPU?","acceptedAnswer":{"@type":"Answer","text":"Yes, Qwen3.8-27B is a 27-billion-parameter dense model designed to run on a single GPU while supporting a 262K token context window. It is released as an open-weight model under the Apache 2.0 license, making it usable for local inference without relying on a hosted API from a closed-source provider. Anyone planning local-first AI setups can follow open-weight model drops like this via daily.dev."}}]} ```