DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to benchmark a Strix Halo machine and share results with Kyojin

Measure prefill and speculative decode speed on your own 128 GB AMD box and export the numbers as JSON.

Authorization notice. Kyojin is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA hardware reviewer or tester with a Ryzen AI Max+ 395 machine who wants to compare its speed with published Kyojin figures.

The problemPublished speed numbers come from one machine, and buyers want to know what their own unit delivers.

The outcomeA benchmark report for your machine that you can compare with the tables in doc/benchmarks.md and submit as a report.

What you need first

  • AMD Ryzen AI Max+ 395 mini PC with 128 GB of memory (Strix Halo, gfx1151)
  • ROCm build of torch, installed per doc/install.md
  • Python and the hf command-line tool to download model packs
  • Roughly 100 GB of free disk space for a model pack (Qwen pack is 95 GB)

Steps

  1. Install ROCm torch and build Kyojin per doc/install.md.
  2. Read doc/benchmarks.md to see how the figures are measured.
  3. tools/bench.sh --json
  4. Compare your prefill and speculative decode numbers with the tables in doc/benchmarks.md.
  5. Send the result through the reporting path in CONTRIBUTING.md.

Prompt for your agent

In the Yamz-Labs/kyojin repo, run tools/bench.sh --json on <target machine> after reading doc/benchmarks.md. Expected output: a JSON benchmark result with prefill and speculative decode tokens per second. Verify that the figures are labeled with the context length and model used before comparing them to the README tables.

Caveat. The README says the published numbers come from one Ryzen AI Max+ 395 with 128 GB, so your results will differ with other hardware and settings.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page