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

How to measure your own machine's speed with janas-bench with Janas

Run janas-bench on your hardware to get tokens-per-second figures and a report for the project.

Who it is forA hardware-curious user or contributor with a CPU or GPU the README did not test, such as a different laptop or an AMD machine.

The problemPublished speeds come from one laptop, so it is unclear how a different CPU, GPU, or disk will perform.

The outcomeYour own reading and writing speeds for a model, plus a benchmark report you can share with the project.

What you need first

  • Linux x86-64 (Ubuntu 22.04, Debian 12 and later) or Windows 10 (1903 or later) or 11, x86-64
  • A terminal on the machine
  • Enough free disk space for the model you pick; the README lists Qwen3-Next-80B at 48.4 GB
  • A machine with 32 GB of RAM is the one the README measured on; other machines are untested

Steps

  1. Complete the install from the Try it section and make sure ./janas-chat runs once
  2. Run the benchmark: janas-bench --prompt 1024 --gen 16
  3. For a steadier figure, run three rounds: janas-bench --rounds 3
  4. Compare the reading and writing tokens-per-second with the README table
  5. Send the report from janas-bench back as described in Helping it run on more hardware

Prompt for your agent

In the janas repo at <install-folder>, run janas-bench --prompt 1024 --gen 16 and then janas-bench --rounds 3. Output the reading and writing tokens-per-second figures for each run. Verify that both runs completed and that the figures are reported as numbers, not errors.

Caveat. The README says figures on another machine will differ and that the benchmark may need several passes before the engine settles on its choices, so a first run is usually slower.

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