Repository navigation
[Benchmark] RX 6900 XT (gfx1030): the released rx6000 package on a real RX 6000 card - #4723
Closed
lvxianchao wants to merge 1 commit into
Closed
lvxianchao wants to merge 1 commit into
lvxianchao wants to merge 1 commit into
Conversation
…al RX 6000 card The rx6000 package has been marked 'built, not tested on a real RX 6000 card' since 0.2.2, and docs/AMD_HIP.md asks for a run with the end of the engine log. This is that run: engine 0.1.54 linux-x86_64-hip-rx6000, no source build, Qwen3.8-Flash-Next IQ3_S, 262144-token context, pictures on (CPU reader), on an RX 6900 XT 16 GB behind a QEMU/KVM guest with GPU passthrough. results: standard protocol strata-qwen38-thinking-v1-draft.1, 12 of 12 sanity checks; prompt 908.5 / 1128.9 tok/s and decode 39.7 / 40.2 tok/s at 4K / 16K. community-notes.md adds measurements outside the protocol: the 2.1x win from STRATA_HIP_PROMPT_F16=1 (488 -> 1029 tok/s prefill, decode unchanged), flat prefill cost from 64K to 512K context, prompts up to 300K tokens, pictures working on gfx1030, and three negative results (worker counts 2/3/4 identical, --ple-io mmap no change) so nobody repeats them. Not a code change: no engine, default or behaviour is touched.
|
Thanks for the pull request. To keep the tracker readable, every item needs an area prefix in the title and the parts of the pull request template filled in. This one is missing:
Edit the pull request (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment Details: CONTRIBUTING.md |
|
Thanks, this follows the format now. |
Owner
|
Thank you for the benchmark. We have collected these results for the benchmarks page on the Strata website, so we are closing this pull request instead of adding the files to the repository. If you measure again, for example on 0.2.11, you are welcome to open a new report. The Strata project |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and result
docs/AMD_HIP.mdmarks therx6000Linux package "built, not tested on a real RX 6000 card", and asks for a run on such a card with the end of the engine log. That run was missing; this PR adds it.Before: no report existed for a real RX 6000 card with the released package, and the RDNA2 section's numbers came only from source-built engines.
After: the released
rx6000package runs on a real Radeon RX 6900 XT (gfx1030) — the standard protocol passes 12 of 12 sanity checks (including all four tool-call checks) at prompt 908.5 / 1,128.9 tok/s and decode 39.7 / 40.2 tok/s (4K / 16K), with IQ3_S at 262,144 tokens of context and pictures on.Related discussion
None open.
CONTRIBUTING.mdallows benchmark reports to go straight to a PR.Approach
Results only, as
CONTRIBUTING.mdasks for. No engine code, default or behaviour is touched.bench/results/2026-10-30-standard-navi-21-rx-6800-6800-xt-6900-x-0f8809de/holds whatstrata bench runwrote:README.md,results.json,outputs.jsonl,config.json,provenance/, plusstrata-iq3_s-session.log(the engine log tail thatdocs/AMD_HIP.mdasks for).community-notes.mdin the same folder holds the measurements made outside the protocol, each labelled as such and not comparable with standard results: theSTRATA_HIP_PROMPT_F16=1before/after, the flat cost of context size from 64K to 512K, prompts up to 300K tokens, pictures on gfx1030, and three negative results so nobody repeats them.docs/COMMUNITY_BENCHMARKS.md.Validation
Passed:
strata bench run --url http://127.0.0.1:8080 --track custom --track-notes "…" --quantization IQ3_S, engine 0.1.54linux-x86_64-hip-rx6000(release package, no source build), run20261030T154543Z-0f8809de. 12 of 12 sanity checks (instruction 4/4, retrieval 4/4, tool calls 4/4), no failed request, 3 min 54 s of measured work after the model loaded. Everything is in the folder above.Failed: none observed.
Not run: the Windows
rdna2package; any quantization other than IQ3_S (IQ3_XXS was not downloaded); bare metal; the concurrency and soak suites;--layer-split(single card); per-request clocks, power and temperatures.Limits
vfio-pci,x-vga=1, q35 + OVMF,cpu: host); the model files sit on the host's NVMe behind virtio. The absolute numbers are therefore not bare-metal numbers. PCIe is Gen4 x16 (LnkSta: Speed 16GT/s, Width x16, Resizable BAR 16 GB).truncatedat the 512-token cap because reasoning used the budget. That is the cap, not a failure, andresults.jsonrecords it.community-notes.mdare one request per cell, not medians, except the tenSTRATA_HIP_PROMPT_F16on-arms. They answer the questions this report raises; they are not a second benchmark.docs/AMD_HIP.md; say the word and I will update it here or in a follow-up, whichever you prefer.