agentleFS
wado-langwado-lang/wado/.claude/skills/benchmark/SKILL.md

benchmark

Skill120 starsChanged 16 days agoMITView on GitHub

Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.

  • Pipes a download into a shell
  • Installs packages

95 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-clean, ios-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 8 projects that use this

  • +1 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 81 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the benchmarks and update benchmark/README.md (and wasm-size/README.md).

    line 8
  2. Very specific:

    Run mise run benchmark-all three times, each to its own log in scratchpad/, then pick per row with mise exec -- node benchmark/pick.ts …

    line 28
  3. Very specific:

    Run http-routing separately (needs oha + pinned cores): SLICE=10 ROUNDS=3 SHAPES="1 4" mise run benchmark-http-routing.

    line 36
  4. Distinctive:

    Update the tables, following README.md's existing layout.

    line 48
  5. Very specific:

    Read the sweep with pick.ts the same way as a best-of-three: it keys rows by (task, implementation, phase), so the "best" column names the …

    line 108
  6. Very specific:

    Read the rate and the ms/iter straight off.

    line 121

“Common” is measured: kept by at least 6 in 10 of the 81 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Benchmark

Run the benchmarks and update benchmark/README.md (and wasm-size/README.md).

Prerequisites

mise run on-task-started
  • vendor/wasmtime submodule must exist (the SessionStart hook handles it; otherwise git submodule update --init --recommend-shallow vendor/wasmtime).
  • http-routing needs oha (cargo install oha); bun is mise-managed.
  • gale-gen's and sqlite-parse's ANTLR4 references need java and javac, which benchmark/mise.toml provides; the jar is fetched to ~/.cache/gale. Those rows are skipped if the tool is absent.
  • wasm-size needs rustup target add wasm32-wasip1 and Moonbit (curl -fsSL https://cli.moonbitlang.com/install/unix.sh | bash, then moon update in each wasm-size/* dir).

Procedure

  1. Run mise run benchmark-all three times, each to its own log in scratchpad/, then pick per row with mise exec -- node benchmark/pick.ts scratchpad/run{1,2,3}.log (throttling only ever slows things down). Use that tool rather than reading the logs by eye: it keys rows by (task, implementation, phase) and selects on ms/iter, so a rate that rounds to a tie across runs cannot pair with the wrong ms/iter. Which benchmarks run, and in what order, is benchmark/mise.toml's all task.
  2. Run http-routing separately (needs oha + pinned cores): SLICE=10 ROUNDS=3 SHAPES="1 4" mise run benchmark-http-routing. It keeps the per-(server, request) max internally, so one invocation suffices, and it measures one worker shape per entry in SHAPES. Add HEADROOM_CHECK=1 when CONNECTIONS_PER_WORKER, OHA_CORE_COUNT or SHAPES changed, to confirm oha was not the ceiling.
  3. Measure the three PGO builds for the README's Profile-Guided Optimization section (see PGO).
  4. Refresh the README Environment line versions: mise exec -- node --version, mise -C benchmark exec -- bun --version, rustc --version, cc --version | head -1. mise -C benchmark ls names wasi-sdk, and wasmtime's version is the vendor/wasmtime workspace version.
  5. Update the tables, following README.md's existing layout. http-routing is req/s (higher is better), one table per worker shape. Keep measured figures inside tables — prose around them is not re-measured and drifts. An input size in the prose comes from the program's own header line, such as gale-gen (Rust): 42786 bytes, so compare each one with the log.
  6. wasm-size: mise run report-wasm-size, then update wasm-size/README.md. mise -C wasm-size ls names Zig, and moon version names Moonbit.
  7. Compare every Wado row with the README's previous figure, and attribute each one that moved (see PGO). Report those to the user.

PGO

A Wado row in the procedure is a PGO build: wado run and wado compile apply the profile in the benchmark's pgo/ by default. benchmark-all runs each one again as its (no-pgo) row, which wado_rows in benchmark/wado.sh prints, and the tables list both. http-routing has no such row, and the README says so. wasm-size has no profile, so a size change is the compiler's or the program's.

The README's PGO section compares three builds, and its commands stand beside its tables. The no-cold-paths wall clock comes from three more runs, alternated with the three of the procedure. benchmark-all and all-wado leave out the table's gale_html row, so run mise run -C benchmark gale-highlight-html the same way.

Compare two builds with mise exec -- node benchmark/ab.ts --base <no-pgo logs> --head <PGO logs>. Its verdict gives the table's noise. It keys rows by implementation, so split a benchmark-all log into one log per build first.

A profile can move a row through what the program allocates, because a change of allocation moves where collections land. wado run --gc-log shows that, and microgpt needs a new heap sweep when it happens.

Two figures from different sessions can differ by noise alone, so attribute a Wado row that moved by an A/B in one session: the compiler that measured the README against this one, with WADO_BIN and ab.ts (see the wado-performance skill). If the verdict is noise, the row did not move. Otherwise read the verdict on its (no-pgo) row. If that moved too, the compiler moved it apart from PGO. If not, PGO moved it: either the row's pgo/ file, or how the compiler uses a profile, such as the thresholds in pgo.rs or the inliner's hot price. git log on each shows what changed, and when both did, isolate them before naming one. http-routing has no (no-pgo) row, so its A/B, which benchmark/http_routing/README.md states, ends at the first verdict.

Whether to record the profile again is a separate decision, and benchmark/AGENTS.md says what a re-recording commits.

Sweeping a compiler knob

WADO_BENCH_FLAGS is appended to every wado compile / wado run the harness issues, so an arm costs a benchmark run rather than a release rebuild:

set -e  # a failed arm would leave pick.ts choosing among the rest
for t in 13 20 32; do
  WADO_BENCH_FLAGS="--optimize-inline-threshold $t" mise run benchmark-all > scratchpad/thr$t.log 2>&1
done
mise exec -- node benchmark/pick.ts scratchpad/thr{13,20,32}.log

Read the sweep with pick.ts the same way as a best-of-three: it keys rows by (task, implementation, phase), so the "best" column names the winning arm per row. Only a knob both wado compile and wado run accept can be swept this way, since the harness passes the flags to both. The knob a sweep settles on is a default in optimize.rs, not a flag the README's numbers were taken under — re-run the suite unflagged before updating the tables.

Comparing the settled default against origin/main is a different measurement, and WADO_BIN plus ab.ts is how: see the wado-performance skill.

Reading output

Each program prints a throughput line — <rate> <unit>/s (<ms> ms/iter, <n> iter) — per phase (zlib prints two phases, Compress:/Decompress:). Read the rate and the ms/iter straight off; the iteration count auto-calibrates to ~1s, so there is no total to report. The unit is the benchmark's own (numbers/s, px/s, conversions/s, MB/s, req/s); vs best = fastest rate / this rate.

Report a change between two measurements with improvement as positive: +9% means faster, -13% slower. This is the sign ab.ts prints.

Each benchmark prints the implementations it compared, so read them off the run rather than from a list here. Two are conditional: the ANTLR4 rows for sqlite-parse and gale-gen are skipped when java is absent, and the run says SKIP: when it drops one.

Workload sizing

Benchmarks auto-calibrate their iteration count to run ~1s, so no manual denomination is needed. A workload whose single iteration approaches that reports one iteration and stops averaging — shrink its problem size, across every language implementation of that benchmark, until it calibrates again.

Notes

  • Tool versions come from mise, not the system.
  • Cloud VMs are noisy; best-of-three absorbs the drift.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.