Skip to content

bench: community report, 2x PH402 SKU 200 (4x GP100, sm_60), Swift 1.5 IQ3_XXS at 1M, --pipeline-windows off vs on over four stages, engine 0.1.41 + patches - #1747

Closed
ruibeikaa wants to merge 2 commits into
Niko1221:mainfrom
ruibeikaa:bench/community-2x-ph402-sku200
Closed

ruibeikaa wants to merge 2 commits into
Niko1221:mainfrom
ruibeikaa:bench/community-2x-ph402-sku200

Conversation

@ruibeikaa

Copy link
Copy Markdown
Contributor

Results-only submission, no engine changes. Adds bench/results/2026-10-09-community-2x-ph402-sku200/ following docs/COMMUNITY_BENCHMARKS.md.

Headline. --pipeline-windows 2 (#1656 + #1674) on a four-stage layer split of four GP100 dies raises decode by +14.6% to +28.8% on 9 prompts of 87 to 301,147 tokens. Some examples:

  • 40.5 → 51.2 tok/s on a 256-token code answer.
  • 47.6 → 61.3 on a 512-token one.
  • 43.2 → 53.7 after a fresh 301,108-token read.
  • 41.7 → 50.3 on a follow-up at 301K.

Prompt reads are unchanged by the flag. Replies are identical bit for bit in all three arms on all 9 prompts.

Hardware:

  • GPUs: 2× NVIDIA PH402 SKU 200, i.e. four GP100 dies (sm_60, 48 SMs, 31.91 GiB each, TCC). Each die has a 140 W cap and an application clock of 1050 MHz.
  • Links: the two dies of a board copy peer-to-peer at 73.0–73.2 GB/s; across boards 3.3 GB/s; host to device 3.3 GB/s per die.
  • Host: Ryzen 9 9950X3D, 256 GiB DDR5, ASUS ProArt B850-CREATOR WIFI NEO, NVMe SSD.
  • OS: Windows 11 (build 26300), driver 581.80, CUDA 12.9.

Software: source builds for sm_60 (-DSTRATA_EXPERIMENTAL_SM60=ON). The server is serve/server.py from v0.1.41.

Model:

Configurations tested (every reply is hashed):

  1. Pipelined windows: next7, next8 without the flag, and next8 with --pipeline-windows 2. One engine start each, the same 9 requests. These include a follow-up at 301K and a return to that conversation from the conversation cache.
  2. Prompt path: next8 vs next9 (the MMQ patch), and STRATA_PREFILL_PIPE 768 / 290 / 450 on next9. Eight starts in bracketed order, 5 requests each (3 in the one start with the prefill timer).
  3. Draft floor: spec_min_p 0.5 / 0.7 / 0.85 / 0.95 per request with pipelining on. 3 prompts × 2 rounds.

Other results:

  • MMQ patch: the batched reads take 2.5–6.0% less time (bracketed next8 / next9 / next8 starts, one run each), and replies are identical.
  • STRATA_PREFILL_PIPE 768 → 290:
    • The 1,158-token read goes from 4.627 / 4.632 s to 4.018 s.
    • The 34,835-token read goes from 48.967 / 49.195 s to 46.545 s.
    • 1,027 tokens appended to that conversation go from 4.339 / 4.348 s to 4.419 s (+1.7%).
    • The changed chunking changes the output bits.
  • Draft floor: 0.85 is the fastest value on both code prompts.
  • Driver check: bench.py (plan ab), run again on next9 at 290, reproduced that arm's 5 reply hashes.

Limitations:

Context:

…5 IQ3_XXS at 1M, --pipeline-windows off vs on over four stages, engine 0.1.41 + patches
The template's section bullets and its results table (configuration, actual prompt, reused and generated tokens,
runs, prompt and decode tok/s median and range, TTFT), generated from the per-run files. The comparison tables
follow as derived data. No measurement changed.
@CC-David-CC

Copy link
Copy Markdown
Contributor

nevermind missed it the first time i read this. perfect. you confirmed exactly what i wanted to check

@Niko1221

Copy link
Copy Markdown
Owner

Thanks for the pull request.

We're resetting the tracker for 0.2.0-beta. There are more than 1,300 open issues and pull requests, too many for us to review properly, so we're closing everything that isn't being worked on right now. Closed here does not mean rejected.

To reopen it takes about two minutes:

  1. Rebase on main if it no longer applies, and re-run your checks on 0.2.0-beta.
  2. Start the title with its area: [Engine], [GUI], [TUI], [Benchmark], [Docs] or [Other].
  3. Fill in the pull request template: the problem and result, and the validation (what you ran, on which revision, what you saw).
  4. Comment /reopen. A check runs and either reopens the pull request or lists what is still missing.

The rules are in CONTRIBUTING.md.

@Niko1221 Niko1221 closed this Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants