Created bymario-alka.dePowered bygodcore.denoob2claw.detricoma.de
Contributed byMario AlkaQwen (Alibaba)

Qwen3.8-Flash-Next

Performance benchmark · measured on 01.10.2026 13:51

Benchmark-IDrun-20261001-120303-5446f0
Timebench 3 - Kombi (Prefill + Generation)MoE180BRuntime: llama.cpp
ℹ
Public note: RAM: 7x 16 GB Samsung DDR4-3200 RDIMM (M393A2K43DB3-CWE) = 112 GB @ 3200 MT/s
Generation35,58tok/s
Prefill219,77tok/s
Time to First Token12.963,00ms
Total duration59,44s
Concurrency1parallel
Ranking in the field
1005of 1695 systems

Performance benchmark · Primary metric: Generation-Speed (tok/s) · 1× concurrent

This run is better than 41 % of all comparable systems.
Generation 35,6 tok/s
-55 % vs Ø 78,3
Prefill 219,8 tok/s
-92 % vs Ø 2.885,6
Time to First Token 12.963 ms
-49 % vs Ø 25.508
Distribution in the field0 – 405 tok/s
Ø 78 Median Dieser Lauf

Wie schlägt sich dieser Benchmark mit anderen Modellen?

How does this benchmark compare on other GPUs?

Same model on different hardware · 1× concurrent · Generation (tok/s)

Hardware

GPU: 2x NVIDIA RTX A6000 · 48 GB VRAM
CPU: AMD EPYC 7203P 8-Core Processor
RAM: 110 GB
Mainboard: ASRockRack ROMED8-2T/BCM

Setup

Runtime: llama.cpp
Quantization: -
Model: Qwen3.8-Flash-Next

Configuration

benchmark-konfiguration — run-20261001-120303-5446f0
# LLM-Benchmark Konfiguration # Modell : Qwen3.8-Flash-Next # Engine : llama.cpp # Run-ID : run-20261001-120303-5446f0 # GPU : 2x NVIDIA RTX A6000 # CPU : AMD EPYC 7203P 8-Core Processor # RAM : 110 GB bench@llm-benchmark:~$ llama-server Qwen3.8-Flash-Next-UD-Q4_K_XL \ -ngl 99 \ --n-cpu-moe 10 '(2xA6000' NVLink, 112GB Samsung 'DDR4-3200)'
Engine?Die Inferenz-Software, die das Modell ausliefert (z.B. vLLM oder llama.cpp). Sie bestimmt Geschwindigkeit, unterstuetzte Modellformate und welche Parameter ueberhaupt verfuegbar sind.llamacpp
GPU-Layer?Anzahl der auf die GPU ausgelagerten Modell-Layer. Hoeher = mehr VRAM und schneller; der Rest laeuft auf der CPU. 999 = alles auf GPU.99
n-cpu-moe10
execution_typelocal

All benchmarks of this model To leaderboard

Anzeige
Model comparison

Qwen3.8-Flash-Next on various hardware

All published performance runs of this model – each bubble a variant: position = prefill (X) × generation (Y), bubble size = number of runs. Closer to the top right = faster. ★ Marked gold = this benchmark.

GPUby graphics card

89,567,445,223,10,9145202260317Prefill (tok/s)Generation (tok/s)AMD Radeon RX 7900 XTX - 18,7 tok/s Generation, 180 tok/s Prefill, TTFT 55.956 ms (3 Laufe)AMD Radeon RX 7900 XTXNVIDIA RTX A6000 - 71,7 tok/s Generation, 282 tok/s Prefill, TTFT 43.934 ms (12 Laufe) | DIESER LAUF★ NVIDIA RTX A6000
★ NVIDIA RTX A6000 71,7 tok/s this runAMD Radeon RX 7900 XTX 18,7 tok/s

CPUby processor

89,567,445,223,10,9145202260317Prefill (tok/s)Generation (tok/s)AMD Ryzen Threadripper PRO 3955WX 16-Cores - 18,7 tok/s Generation, 180 tok/s Prefill, TTFT 55.956 ms (3 Laufe)AMD Ryzen Threadrippe...AMD EPYC 7203P 8-Core Processor - 71,7 tok/s Generation, 282 tok/s Prefill, TTFT 43.934 ms (12 Laufe) | DIESER LAUF★ AMD EPYC 7203P 8-Core...
★ AMD EPYC 7203P 8-Core Processor 71,7 tok/s this runAMD Ryzen Threadripper PRO 3955WX 16-Cores 18,7 tok/s

MBby mainboard

86,269,953,637,321,0105225344464Prefill (tok/s)Generation (tok/s)ASUSTeK COMPUTER INC. Pro WS WRX80E-SAGE SE WIFI - 35,4 tok/s Generation, 170 tok/s Prefill, TTFT 59.933 ms (9 Laufe)ASUSTeK COMPUTER INC....ASRockRack ROMED8-2T/BCM - 71,7 tok/s Generation, 399 tok/s Prefill, TTFT 25.947 ms (6 Laufe) | DIESER LAUF★ ASRockRack ROMED8-2T/...
★ ASRockRack ROMED8-2T/BCM 71,7 tok/s this runASUSTeK COMPUTER INC. Pro WS WRX80E-SAGE SE WIFI 35,4 tok/s

ENGby engine

78,975,371,768,164,6246256267277Prefill (tok/s)Generation (tok/s)llama.cpp - 71,7 tok/s Generation, 262 tok/s Prefill, TTFT 46.339 ms (15 Laufe) | DIESER LAUF★ llama.cpp
★ llama.cpp 71,7 tok/s this run

DRVby driver

78,975,371,768,164,6246256267277Prefill (tok/s)Generation (tok/s)unbekannt - 71,7 tok/s Generation, 262 tok/s Prefill, TTFT 46.339 ms (15 Laufe)unbekannt
unbekannt 71,7 tok/s
💰 Economics

Economics of this run

Operating cost, TCO and comparison with the next-best runs of the same model at identical concurrency (1× concurrent). Methodology →

⚙️ ConfigurationAll metrics and charts below follow these settings – based on a 24-month runtime.Save to URLReset
⚡ Electricity price EUR/kWh
⚙️ System utilization 100 %
🖥️ Acquisition EUR
🔌 Idle 30 W
⚡ TDP 600 W
☁️ External LLM (API)
Electricity0.30 EUR/kWh
Avg power (incl. idle)600 W estimated (TDP)GPU 600 W full load
Avg cost / hourEUR 0.18
Electricity / 1M tokensEUR 1.41
Token / kWh213.48K
Acquisition (system)EUR 6,180 partial priceGPU EUR 6,000 · PSU EUR 180
Electricity (2 years)–
TCO (2 years)EUR 9,334
Output tokens (2 years)2.24B
☁️ External LLM (API) – comparison
External LLM cost (2 years)–
Savings vs. external (2 years)–

All values above and the charts below take the configured system utilization into account: at X% the system generates only X% of the time, the rest it idles (30 W). Cost per hour drops (more idle), cost per token rises.

Cost over 2 years – electricity only

Cost over 2 years – incl. acquisition (TCO)

Speed vs. tokens per euro

Euro per 1M tokens

Comparison vs. API – economics per benchmark

Qwen3.8-Flash-Next2x NVIDIA RTX A6000Qwen3.8-Flash-Next2x NVIDIA RTX A6000Qwen3.8-Flash-Next2x NVIDIA RTX A6000Qwen3.8-Flash-Next2x AMD Radeon RX 7900 XTX
Electricity cost (24 mo.)––––
Acquisition cost––––
Total cost (TCO)––––
Generated tokens (24 mo.)––––
Token price via API––––
Break-even point (days)––––
Result (savings / extra cost)––––

Comparison with up to 3 next-best runs of this model at the same concurrency (at least one on different hardware). Power = GPU TDP + CPU (idle + 15 %) + board (estimated), acquisition = full system (GPU + CPU + board + RAM + PSU), prices = stored market prices.

Contributed by

Mario Alka Administrator

@marioalka

Ich bin Unternehmer, Softwareentwickler und KI-Enthusiast. Seit vielen Jahren entwickle ich Unternehmenssoftware und beschäftige mich inzwischen fast täglich mit lokalen LLMs, KI-Agenten und leistungsfähiger KI-Hardware.

Mit LLM-Benchmark.de möchte ich eine Plattform schaffen, auf der Modelle, GPUs und Agenten objektiv und reproduzierbar miteinander verglichen werden.