反馈 / #2095
#2095 Community benchmark: RTX 3090, Qwen3.8 Flash-Next IQ3_S, Strata 0.1.43
open · @QuantBox723 · 0 评论 · 去 GitHub 看
BenchmarksSetup & installAMD / HIPNVIDIA / CUDAModels & quantsWindows
说明
# Community benchmark on NVIDIA GeForce RTX 3090 Measured on 2026-10-12 with `tools/strata_bench.py` (suite 1, 3 runs per test, medians with ranges). Speeds are the engine's own timings; first-token times are measured by the client over HTTP. Speed only: no correctness check was run. ## Hardware and software - GPU and VRAM: NVIDIA GeForce RTX 3090, 24 GiB VRAM - CPU: Intel(R) Xeon(R) CPU E5-2696 v4 @ 2.20GHz (22 cores, 44 threads); installed RAM: 127.8 GiB; storage: not measured - OS: Windows 11 (10.0.26300); GPU driver: 610.88; CUDA: not read - Strata: project 0.1.43, commit 7695859a; engine 0.1.43 - Background workloads and power limits: not recorded ## Model and configuration - Model and quantization: qwen3.8-flash-next-iq3_s - Context: 262144 tokens; parallel slots: 1 - Settings: the install's own configuration, unchanged; thinking off for the suite; temperature 0 ## Method Run by `python tools/strata_bench.py --long` against the HTTP API of a Strata server (already running); model loading is not timed. One warm-up chat and a 1K prompt are discarded first. Every prompt starts with a unique tag, so the conversation cache cannot help the fresh-prompt tests. - short chat: the three questions of `tools/ab_engine.py`, up to 100 new tokens, 3 runs - 4K / 16K prompts: generated word lists sized by a calibration request, 24 new tokens, 3 fresh prompts each - agent session: system prompt and four tools, then 5 turns that each add about 1500 words of a project file and continue from the model's own earlier answers (the way agent clients resend a conversation), 64 new tokens per turn, 3 sessions; the cache numbers come from the answer's usage (`cached_tokens`) and timings (`prompt_n`) - concurrency (when run): N requests sent at the same moment, total tokens over the wall time of the burst, latency over all requests ## Results | Configuration | Actual prompt tokens | Reused tokens | Generated tokens | Runs | Prompt tok/s median and range | Decode tok/s median and range | TTFT seconds median and range | | --- | ---: | ---: | ---: | ---: | --- | --- | --- | | short chat | 46 (43-51) | 0 | 100 (100-100) | 9 | not measured | 82.5 (71.1-92.1) | 0.40 (0.33-0.46) | | 4K prompt, fresh | 4019 (4019-4019) | 0 (0-0) | 24 cap | 3 | 1155.6 (1123.8-1158.5) | not measured | 3.51 (3.50-3.61) | | 16K prompt, fresh | 16058 (16058-16058) | 0 (0-0) | 24 cap | 3 | 2111.9 (2098.1-2116.9) | not measured | 7.68 (7.63-7.70) | | 32K prompt, fresh | 32049 (32049-32049) | 0 (0-0) | 24 cap | 3 | 2120.0 (2119.8-2127.6) | not measured | 15.20 (15.14-15.20) | | agent session, follow-up turns | 14469 (14440-14476) at the last turn | see below | up to 64 | 3 | see below | 84.6 (71.1-109.9) | 3.51 (3.32-3.75) | Ranges are the lowest and highest of the runs; `Runs` counts requests that returned a token. ### Agent session (conversation cache) Cache hit over the follow-up turns: 68.6 % (68.5-68.8); earlier-turn tokens read again per session: 74 (4-144) (earlier turns that the cache did not hold; the 13633 (13633-13634) new tokens of the files are read once); first turn (nothing cached) first token: 1.51 s (1.48-1.54). | Turn (run 1) | Prompt tokens | Reused | Read | Prompt tok/s | First token (s) | Decode tok/s | | ---: | ---: | ---: | ---: | ---: | ---: | ---: | | 0 | 609 | 0 | 609 | 408.5 | 1.54 | 65.6 | | 1 | 3712 | 631 | 3081 | 830.7 | 3.746 | 82.8 | | 2 | 5245 | 3775 | 1470 | 435.1 | 3.413 | 80.1 | | 3 | 8689 | 5238 | 3451 | 928.9 | 3.755 | 71.1 | | 4 | 11592 | 8732 | 2860 | 792.6 | 3.652 | 77.1 | | 5 | 14440 | 11594 | 2846 | 806.9 | 3.596 | 84.1 | Per-request data: `results.json`. Engine log lines from the start: `engine-log-excerpt.txt` (when this run started the server). ## Correctness and limitations Not measured: this is a speed suite. The conversation uses the model's own replies, so token counts differ a little between runs. Machine details come from the server, `nvidia-smi`/`rocm-smi` and the OS; background load and power limits are not recorded. Total time of the suite: 169 s.
本站相关内容
相关页面的快捷入口。