# Benchmarks and memory tests LangCheck has three sets of performance checks besides its unit and end-to-end tests: the core's own (Rust), the VS Code extension's end-to-end benchmarks, and the browser extension's benchmarks, memory bounds and soak. None of them run in CI: timings depend on the machine and on what else it is doing. They are a record of what each case costs, and a ceiling far above a normal run that only something broken (a quadratic step, a cache that never hits, a hang) reaches. The two editor harnesses share their generated documents and their recorder: `extension/src/test/e2e/bench/corpus.ts` (seeded generators, so each run checks text the core has never seen) and `extension/src/test/e2e/bench/measure.ts` (median, spread, ceilings, one JSON line per metric). ## Running them | What | Command | Results | | --- | --- | --- | | VS Code: documents and workspaces | `cd extension && pnpm run bench:e2e` | `extension/.vscode-test/bench/results.jsonl` | | Browser: documents on Overleaf and Typst | `cd web && pnpm run bench documents` | `web/.bench/results.jsonl` | | Browser: memory at the edges | `cd web && pnpm run bench memory` | `web/.bench/results.jsonl` | | Browser: soak | `cd web && SOAK_MINUTES=60 pnpm run bench soak` | `web/.bench/results.jsonl`, `web/.bench/soak-