NewsHive
CONTACT USANALYST PORTAL →
aiBACKGROUND

What speed is everyone getting on Qwen3.6 27b?

BACKGROUND
4 SIGNALSFIRST DETECTED 22 April 2026UPDATED 5 May 2026
The NewsHive View

On April 22nd, someone on LocalLLaMA posted the kind of question that matters more than most official benchmarks: what speed is everyone actually getting on Qwen3 27B? Not theoretical throughput on server-grade iron. Real tokens per second, on real hardware, in real living rooms and home offices where the electricity meter is ticking. The thread that followed is the community doing what communities do best — turning anecdote into data by sheer volume. RTX 4090 owners dropping their numbers. Dual-GPU setups wrestling with the overhead of tensor splitting across PCIe lanes, where the interconnect often costs you more than it gives back. Apple Silicon users on M2 and M3 chips where unified memory architecture changes the equation entirely, letting a 27B model breathe in a way that discrete GPU setups with constrained VRAM simply cannot. The question itself signals something: Qwen3 27B has reached the threshold of widespread local adoption, which is where the real stress-testing happens and where the gap between promise and performance either closes or widens.

If confirmed as representative, here is what this means. The performance floor matters as much as the ceiling. If users are getting comfortable, usable speeds — even modest ones — on consumer hardware, that accelerates the broader shift away from API dependency toward genuinely local inference. A 27B model running at 15 to 20 tokens per second on an RTX 4090 is a different proposition than one that crawls. It changes what workflows are practical, what privacy considerations become tractable, and what the realistic competitive pressure on cloud providers looks like. Hardware manufacturers and quantization tooling developers — the people building llama.cpp, Ollama, and their successors — get immediate, unfiltered signal about where the bottlenecks live. That feedback loop is fast, and it moves models and runtimes forward in ways that no internal benchmark suite fully anticipates.

Watch for consolidated speed reports from multiple hardware configurations that would let the community build a reliable performance matrix for Qwen3 27B — and watch for whether quantization format choices, particularly Q4 versus Q8, emerge as the decisive variable in the conversation.

How the story developed
20 Jun
22 Apr
3.4
Other feeds and industry voices
26 Mar
1 million tokens per second from a single cluster, what that actually means

<!-- SC_OFF --><div class="md"><p>Got Qwen 3.5 27B to 1,103,941 tok/s on 12 nodes with 96 B200 GPUs.</p> <p>At that rate you process 50,000 insurance policy documents in hours

OPINION · WHAT · singularityOPEN STORY
8 Apr
Napkin math: KV cache for Llama 3.1 at 128K context is ~64GB per decode request, and that's after GQA

<!-- SC_OFF --><div class="md"><p>Every output token the model generates requires reading the entire KV cache from High Bandwidth Memory.</p> <p>Here's what that actually looks

OPINION · WHAT · LocalLLaMAOPEN STORY
25 Mar
Qwen3.5-397B-A17B reaches 20 t/s TG and 700t/s PP with a 5090

<!-- SC_OFF --><div class="md"><p>I could not find good data points on what speed one could get with a single 5090 and enough DDR4 RAM. </p> <p>My system: AMD EPYC 7532 32core

OPINION · WHAT · LocalLLaMAOPEN STORY
5 May
MTP on strix halo with llama.cpp (PR #22673)

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1t4uj9h/mtp_on_strix_halo_with_llamacpp_pr_22673/"> <img alt="MTP on strix halo with llama.cpp (PR #22673)"

OPINION · WHAT · LocalLLaMAOPEN STORY
24 Mar
FlashAttention-4: 1613 TFLOPs/s, 2.7x faster than Triton, written in Python. What it means for inference.

<!-- SC_OFF --><div class="md"><p>Wrote a deep dive on <strong>FlashAttention-4 (03/05/2026)</strong> that's relevant for anyone thinking about inference performance.</p>

OPINION · WHAT · LocalLLaMAOPEN STORY
13 Apr
FYI, Step 3.5 Flash has better perf and context is 1/4 the price in llama.cpp

<!-- SC_OFF --><div class="md"><p>So i recently updated LMstudio after a long pause and updated my llama.cpp runtimes too.. i was shocked.. i thought maybe something like

OPINION · WHAT · LocalLLaMAOPEN STORY
10 Apr
How are you handling KV cache memory pressure in production? HBM keeps filling up

<!-- SC_OFF --><div class="md"><p>Running Llama-3-70B with long contexts and hitting HBM limits constantly. 128K context burns approx 40GB just for KV cache — half the H100 gone

OPINION · HOW · LocalLLaMAOPEN STORY
5 May
Smaller gguf getting way less tokens per second?? So confused!

<!-- SC_OFF --><div class="md"><p>Noob here, Running Qwen3.6 35B A3B in LM Studio on a 3080 10GB + Ryzen 5 3600 on Windows 10.</p> <p>Tried some unsloth quants with identical

OPINION · WHAT · LocalLLaMAOPEN STORY
Sources
LocalLLaMA×4

NewsHive monitors these sources continuously. All signal titles above link to the original reporting.

Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →