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

Qwen3.8-Flash-Next

Performance benchmark · measured on 25.09.2026 13:08

Benchmark-IDrun-20260925-112847-aca38f
Timebench 3 - Kombi (Prefill + Generation)MoE180BRuntime: llama.cppQuantisierung: UD-Q4_K_XL
Generation22,67tok/s
Prefill123,91tok/s
Time to First Token18.211,00ms
Total duration126,80s
Concurrency1parallel
Ranking in the field
1220of 1660 systems

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

This run is better than 27 % of all comparable systems.
Generation 22,7 tok/s
-71 % vs Ø 78,6
Prefill 123,9 tok/s
-96 % vs Ø 2.837,0
Time to First Token 18.211 ms
-30 % vs Ø 25.989
Distribution in the field0 – 405 tok/s
Ø 79 Median Dieser Lauf

Wie schlägt sich dieser Benchmark mit anderen Modellen?

Hardware

GPU: 2x NVIDIA RTX A6000 · 48 GB VRAM
CPU: AMD EPYC 7203P 8-Core Processor
RAM: 31 GB
Mainboard: ASUSTeK COMPUTER INC. Pro WS WRX80E-SAGE SE WIFI

Setup

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

Configuration

benchmark-konfiguration — run-20260925-112847-aca38f
# LLM-Benchmark Konfiguration # Modell : Qwen3.8-Flash-Next # Engine : llama.cpp # Run-ID : run-20260925-112847-aca38f # GPU : 2x NVIDIA RTX A6000 # CPU : AMD EPYC 7203P 8-Core Processor # RAM : 31 GB bench@llm-benchmark:~$ llama-server Qwen3.8-Flash-Next-UD-Q4_K_XL \ -ngl 99 \ --n-cpu-moe 10 \ -fa on '(2x' A6000 NVLink + 31GB RAM 'Offload)'
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
faon

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

39,037,235,433,731,9155161168175Prefill (tok/s)Generation (tok/s)NVIDIA RTX A6000 - 35,4 tok/s Generation, 165 tok/s Prefill, TTFT 61.921 ms (6 Laufe) | DIESER LAUF★ NVIDIA RTX A6000
★ NVIDIA RTX A6000 35,4 tok/s this run

CPUby processor

39,037,235,433,731,9155161168175Prefill (tok/s)Generation (tok/s)AMD EPYC 7203P 8-Core Processor - 35,4 tok/s Generation, 165 tok/s Prefill, TTFT 61.921 ms (6 Laufe) | DIESER LAUF★ AMD EPYC 7203P 8-Core...
★ AMD EPYC 7203P 8-Core Processor 35,4 tok/s this run

MBby mainboard

39,037,235,433,731,9155161168175Prefill (tok/s)Generation (tok/s)ASUSTeK COMPUTER INC. Pro WS WRX80E-SAGE SE WIFI - 35,4 tok/s Generation, 165 tok/s Prefill, TTFT 61.921 ms (6 Laufe) | DIESER LAUF★ ASUSTeK COMPUTER INC....
★ ASUSTeK COMPUTER INC. Pro WS WRX80E-SAGE SE WIFI 35,4 tok/s this run

ENGby engine

39,037,235,433,731,9155161168175Prefill (tok/s)Generation (tok/s)llama.cpp - 35,4 tok/s Generation, 165 tok/s Prefill, TTFT 61.921 ms (6 Laufe) | DIESER LAUF★ llama.cpp
★ llama.cpp 35,4 tok/s this run

DRVby driver

39,037,235,433,731,9155161168175Prefill (tok/s)Generation (tok/s)unbekannt - 35,4 tok/s Generation, 165 tok/s Prefill, TTFT 61.921 ms (6 Laufe)unbekannt
unbekannt 35,4 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 40 W
⚡ TDP 610 W
☁️ External LLM (API)
Electricity0.30 EUR/kWh
Avg power (incl. idle)610 W estimated (TDP)GPU 600 + Board 10 W full load
Avg cost / hourEUR 0.18
Electricity / 1M tokensEUR 2.24
Token / kWh133.79K
Acquisition (system)EUR 6,428 partial priceGPU EUR 6,000 · RAM EUR 248 · PSU EUR 180
Electricity (2 years)–
TCO (2 years)EUR 9,634
Output tokens (2 years)1.43B
☁️ 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 (40 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 A6000
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.