Skip to content

bench: RX 7900 XTX + 6800 XT helper layout, 1M and long-output results - #1459

Closed
saikiran-rs wants to merge 2 commits into
Niko1221:mainfrom
saikiran-rs:community/amd-helper-1m-report-20261007
Closed

saikiran-rs wants to merge 2 commits into
Niko1221:mainfrom
saikiran-rs:community/amd-helper-1m-report-20261007

Conversation

@saikiran-rs

Copy link
Copy Markdown
Contributor

Results-only community report for a Linux RX 7900 XTX + RX 6800 XT helper layout with a Xeon E5-2696 v4 and 121 GiB OS-visible RAM.

Measurements

  • Three 8192-token coding generations: 97.2 / 96.7 / 97.0 tok/s. Long prose: 65.0 / 63.9, with actual output lengths retained. The original 100TG gate failed.
  • Full usable1M request: 1048064 input +504 generated +8 API-reserved tokens; all three recall markers found. PP591.7 vs587.4 baseline, full-depth decode39.2 vs39.3.
  • Matched first200 HellaSwag/WinoGrande sample: baseline181/173, final181/175, zero unparseable answers/errors.

Reproduction and limits

Includes exact compressed prompts, per-request engine/client timings, actual token counts, portable configs, pinned model URLs/hashes, source/build provenance and a standalone client/quality harness. Historical source revisions are preserved on the contributor's fork. Offline fixture hashes and pinned-API token counts were checked; the SSE parser was tested with a synthetic stream.

These are historical measurements from a combined0.1.40.2-derived research build, not isolated measurements of a new PR or stock0.1.40.3. All changed settings and inherited contributor work are identified. Q8-kernel-only whole-model results include regressions. The separately managed NVIDIA service's host load was not isolated. No new inference was run for publication.

This report follows docs/COMMUNITY_BENCHMARKS.md and is separate from the helper-allowance engine proposal. No universal speedup or general quality equivalence is claimed.

Maddoxkkm added a commit to Maddoxkkm/Strata that referenced this pull request Oct 11, 2026
The four gfx1100 community issues (Niko1221#1655 Niko1221#1459 Niko1221#1406 Niko1221#1292) were read in full and triaged to this box; the
useful part is in scratch/reports/COMMUNITY-KNOBS.md. Measured here at 16K, matched budgets:

  base                                    1,870.9 tok/s
  +STRATA_RAM_ADAPT=1                     1,950.7  (+4.3%)
  +STRATA_PA_FAST=1 +PF_SWITCH_MIN_T=4096 1,979.0  (+5.8%)
  +STRATA_PF_GEMM=1 +PF_PAD=1             1,990.1  (+6.4%)
  +--prefill 32768                        1,919.0  (+2.6%)
  +STRATA_PF_FUSED=1                      1,898.2  (+1.5%)

Combined (the three winners) 2,012.9 at 16K (+6.4%) and 945.3 at 4K (-0.1%); a 32K chunk adds nothing on
top. All these are bit-changing switches, so switches-accuracy.py grades answers off vs on: the 16K needle
passes in both and the one differing case ('strata' backwards) is flaky off AND on (3/5 each) - the 2-bit
model, not the switches. Everything adopted; 73K real text through the server is now 1,784.3 tok/s
(+7.8% today, +41% over the session's 1,264.5).

Two corrections to the docs, from measurement: the WMMA/SIMT switches labelled gfx12 act on gfx1100, and
on-device kernel-shape autotuning was a no-op here exactly as Niko1221#1292 reports.

Also fixed, after this box hard-froze: stop-server.bat killed a fixed list of old binary names, so newer A/B
engines leaked (~12 GiB each) until free RAM hit 0.0 GiB. It now kills any strata*.exe plus tune_decode, and
the lessons (one engine at a time, budget as a validity gate, the RAM tier being the top lever) are in the
strata-local-tuning skill.
@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.

2 participants