Skip to content

Benchmark large-repo performance and publish the numbers #475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jonassaa merged 3 commits into from
Sep 17, 2026
Merged

Benchmark large-repo performance and publish the numbers #475

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5ebe990
feat(bench): deterministic fixtures and a large-repo benchmark harness
jonassaa Sep 17, 2026
c898b89
docs(perf): publish the first run, and what it found
jonassaa Sep 17, 2026
4817065
test: hold the published performance numbers to one measured run
jonassaa Sep 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,10 @@ to what you are reading. A new section here needs a reason a pointer cannot serv
and credentials, signing, stash, spawning processes, bisect, async/threading.
- `docs/dev/distribution.md` — `pgit` CLI packaging per channel, the launch
detach, Tauri permissions.
- `docs/dev/performance.md` — the large-repo benchmark: the fixtures, what each
number does and does not include, the baseline it is compared against, and
the published results. Read it before touching the log walk, `status`, or
the refresh path, and re-run `pnpm bench` when you do.
- `docs/dev/releasing.md` — what a version number means and when to bump which
part, the cut-a-release runbook (changelog lands on `main` FIRST), and the
prerelease-promotion traps. Read it before tagging anything.
Expand Down Expand Up @@ -58,6 +62,7 @@ pnpm test # vitest (unit logic + component tes
pnpm test:e2e:docker # e2e — THE way to run e2e (headless, same stack as CI)
pnpm test:e2e:docker run --spec e2e/specs/X.e2e.ts # ...one spec against this worktree's snapshot
pnpm exec tsc -p e2e/tsconfig.json --noEmit # e2e typecheck gate (root tsc excludes e2e/)
pnpm bench # large-repo benchmark (docs/dev/performance.md)
```

**Local production builds need the updater signing key.** `tauri.conf.json`
Expand Down
15 changes: 15 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,6 +171,21 @@ Add them alongside the code you change:
- New component → `*.test.tsx`.
- New user-facing flow, or a bug that reached the UI → an e2e spec.

### Measuring performance

Performance is measured rather than tested, and it is not a CI gate — wall clock
on a shared runner is a flake generator.

```bash
pnpm bench # three generated fixtures, built in seconds
pnpm bench --linux # …plus a real clone of torvalds/linux (multi-GB)
```

Run it on a quiet machine if you have touched the log walk, `status` or the
refresh path, and commit what it writes — `docs/dev/performance.md` explains
what each number does and does not include, and the figures on the website come
from the same run.

## Production bundles

```bash
Expand Down
Loading