Claim
Qwen3.6-35B-A3B Q4_K_M on Ryzen AI Max+ 395 (llama.cpp Vulkan) — time to the first token of any output: 212 ms
212ms
The measurement
On a Beelink GTR9 Pro — AMD Ryzen AI Max+ 395, Radeon 8060S (gfx1151), 128 GB LPDDR5X-8000 unified running llama.cpp (server, Vulkan backend), b9049 (server_fingerprint b9049-2496f9c14) with ggml-org/Qwen3.6-35B-A3B-GGUF @ baec3ebee244 (Q4_K_M), the measured time to the first token of any output was 212 ms (median over all valid requests of three cells). The measurement was taken under the frozen interactive-assistant-v2@2026-08-02 workload; evidence level lab_unit_replicated, 18 valid runs across 2 physical units. The value is re-derived from the raw run records on every CI build.
Statement
Median client-side time to the first streamed token of any kind, across all three operating settings on the human-task corpus. Evidence
- System
- Beelink GTR9 Pro — AMD Ryzen AI Max+ 395, Radeon 8060S (gfx1151), 128 GB LPDDR5X-8000 unified
- Runtime
- llama.cpp (server, Vulkan backend), b9049 (server_fingerprint b9049-2496f9c14)
- Model artifact
- ggml-org/Qwen3.6-35B-A3B-GGUF @ baec3ebee244 (Q4_K_M)
- Scope
- interactive-assistant-v2@2026-08-02
- Aggregation
- median over all valid requests of three cells
- Evidence level
- lab_unit_replicated
- Status
- active
- Limitations
- Nine runs across three cells across two commercially identical units — repeated, not unit-replicated.
- Runs
-
- run-20260802-v2-nothink-a
- run-20260802-v2-nothink-a-r2
- run-20260802-v2-nothink-a-r3
- run-20260802-v2-budget4k-a
- run-20260802-v2-budget4k-a-r2
- run-20260802-v2-budget4k-a-r3
- run-20260802-v2-budget1k-a
- run-20260802-v2-budget1k-a-r2
- run-20260802-v2-budget1k-a-r3
- run-20260803-v2-nothink-b
- run-20260803-v2-nothink-b-r2
- run-20260803-v2-nothink-b-r3
- run-20260803-v2-budget1k-b
- run-20260803-v2-budget1k-b-r2
- run-20260803-v2-budget1k-b-r3
- run-20260803-v2-budget4k-b
- run-20260803-v2-budget4k-b-r2
- run-20260803-v2-budget4k-b-r3
Derivation
The value is re-derived from the raw run records by this query on every CI build — a published number cannot silently drift from its evidence.
Cite this claim
AGmind Systems Lab. "Median client-side time to the first streamed token of any kind, across all three operating settings on the human-task corpus." Claim strix.qwen36.interactive2.c1.ttft-any-token (212 ms), evidence level lab_unit_replicated, scope interactive-assistant-v2@2026-08-02. https://agmind.ai/claims/strix.qwen36.interactive2.c1.ttft-any-token/ @misc{agmind_strix_qwen36_interactive2_c1_ttft_any_token,
author = {{AGmind Systems Lab}},
title = {Median client-side time to the first streamed token of any kind, across all three operating settings on the human-task corpus.},
howpublished = {\url{https://agmind.ai/claims/strix.qwen36.interactive2.c1.ttft-any-token/}},
note = {Claim strix.qwen36.interactive2.c1.ttft-any-token: 212 ms; evidence level lab\_unit\_replicated; scope interactive-assistant-v2@2026-08-02},
year = {2026}
} Machine-readable: /claims/strix.qwen36.interactive2.c1.ttft-any-token.json · full registry
Own comparable hardware? This claim can be reproduced: /reproduce/
Corrections to published results are logged publicly: errata
← All claims