Benchmark

ttsc publishes two benchmark tracks.

Code Graph (MCP)

The Code Graph benchmark measures whether an agent spends fewer tokens and tool calls when @ttsc/graph is available. It also checks structural coverage: how completely the graph resolves cross-file relationships in a real TypeScript project.

The overview below uses the same shared onboarding prompt across every project with Codex GPT-5.6 terra. The detailed page follows with model tabs, project-specific prompts, and structural coverage.

Loading graph benchmark results...

Compiler Performance

The compiler-performance benchmark measures wall-clock time when a real TypeScript project moves from the legacy tsc + eslint path to TypeScript-Go backed builds, checks, and linting. The dashboard covers build, type-check, lint, and format across real open-source repositories, single-threaded and multi-threaded.

vscode, 6,093 TypeScript files across a large application monorepo, is the flagship example. At 8 checker workers, ttsc builds vscode in around 8 s versus roughly 94 s for legacy tsc, and type-checks it in around 6.5 s versus roughly 73 s. The full dashboard covers nestjs, vue, zod, typeorm, rxjs, and shopping-backend as well.