Skip to content

docs: record the unified engine final measurement on GB10 - #2226

Merged
inureyes merged 1 commit into
mainfrom
docs/epic-2166-final-measurement
Oct 8, 2026
Merged

inureyes merged 1 commit into
mainfrom
docs/epic-2166-final-measurement

Conversation

@inureyes

@inureyes inureyes commented Oct 8, 2026

Copy link
Copy Markdown
Member

Summary

End-of-run measurement for epic #2166 (ADR 0007's regression threshold and the speed questions the phases left open), on GB10 against two release builds: the pre-epic CxxGenerator build (4c44e31, PR #2194) and the final engine build (30ceea2, PR #2225). Adds docs/benchmark_results/unified-engine-final-gb10-2026-10-08.md, its raw records and drivers under docs/benchmark_results/data/unified-engine-final-gb10-2026-10-08/, and an index entry in docs/benchmarks.md. No code changes.

Results

  • mlxcel generate (the engine's DirectEngine client) decodes within the 1.0 percent threshold in every cell: +0.82 and +0.31 percent on Qwen3-1.7B (256 and 8192-token prompts), +0.51 and +0.19 percent on Llama-3.2-1B. TTFT at 256 tokens is about 1 ms higher (+4.4 percent unresolved on Qwen3, +9.0 percent on Llama).
  • The server engine at B=1 with dense storage, the path mlxcel run and chat take since refactor: route mlxcel run and chat through the in-process server engine #2173, is 1.14 to 2.05 percent below the pre-epic CLI and misses the threshold in three of four cells. Phase 0 measured the same scheduler overhead before the epic, but run used CxxGenerator then, so run users see a 1 to 2 percent decode regression.
  • The server's default single-stream configuration (paged at --parallel 4) decodes as before; its 8192-token TTFT dropped 19 percent (Qwen3) and 12 percent (Llama) with the 2048-token chunk.
  • Batched serving: unchanged on Qwen3 defaults; Llama with Turbo4 KV is 16 and 18 percent higher at concurrency 4 and 8.
  • Prefill chunk under live decode (four streams, one 8192-token admission, Llama): 2048 gives about 2.0 s admitted TTFT and 128 ms live-stream p95 ITL; 512 gives about 3.9 s and 56 ms. A policy trade, not a speed win.
  • Gemma 3 paged vs dense under concurrency: dense 1 to 2 percent higher with overlapping ranges, unresolved; default unchanged.

Test plan

  • Single-stream: scripts/engine_bench_rounds.py, 5 interleaved rounds with a null arm and the quiet-host gate, both builds through pick.sh, under the host gpu-lock with no other GPU work
  • Serving: scripts/bench_serving_concurrency.py and scripts/bench_mixed_step_admission.py, 3 alternating rounds per arm

Part of #2166

End-of-run measurement for epic #2166 against the pre-epic CxxGenerator build (4c44e31) and the final engine build (30ceea2), with the raw records and drivers.

- mlxcel generate decodes within the 1.0 percent threshold in every cell (+0.19 to +0.82 percent).
- The server engine at B=1 with dense storage, the path mlxcel run and chat take since #2173, is 1.1 to 2.1 percent below the pre-epic CLI, the same scheduler overhead Phase 0 measured, and misses the threshold in three of four cells.
- Batched serving is unchanged on Qwen3 and 16 to 18 percent higher with Turbo4 at concurrency 4 and 8.
- Prefill chunk 2048 vs 512 under live decode: 2048 halves the admitted request's TTFT and raises live streams' p95 ITL 2.3 times.
- Gemma 3 paged vs dense under concurrency is unresolved.
@inureyes inureyes added type:docs Documentation improvements or additions priority:medium Medium priority status:review Under review area:benchmark Benchmark harness and performance measurement (bench_*.sh, /update-benchmarks) labels Oct 8, 2026
@inureyes inureyes added status:done Completed and removed status:review Under review labels Oct 8, 2026
@inureyes
inureyes merged commit ad84435 into main Oct 8, 2026
27 checks passed
@inureyes
inureyes deleted the docs/epic-2166-final-measurement branch October 8, 2026 01:29
inureyes added a commit that referenced this pull request Oct 8, 2026
…nt (#2231)

## Summary

One-line correction to `docs/benchmark_results/unified-engine-final-gb10-2026-10-08.md` (PR #2226). The server engine at B=1 with dense storage measured -1.44, -1.14, -1.24 and -2.05 percent against the pre-epic CLI. That misses the -1.0 percent threshold in all four cells, not in three as the summary line said. The table was already correct. The follow-up is #2227.

## Test plan

- [x] Text-only change; the table values are unchanged

Part of #2166
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:benchmark Benchmark harness and performance measurement (bench_*.sh, /update-benchmarks) priority:medium Medium priority status:done Completed type:docs Documentation improvements or additions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant