New analysis History State reference

loading

culprit — performance regression detective

New analysis History State reference GitHub

Powered by VYBEX

Find a performance regression

Give it a repo and a benchmark command. It bisects the commit history, diagnoses the guilty commit, and tries to fix it — and proves the fix with a real re-run.

See it work in about a minute

A bundled repo with a real history of 20 commits and one genuine N+1 regression hidden in a “simplify loading” refactor. Every benchmark number is a real measurement.

RepositoryAn https:// or ssh git URL the backend can clone.Benchmark commandRun at every commit; must print a single wall-clock number (ms) as its last line.Test command (optional)A fix only counts as verified if this still exits 0 on the patched code — so a fast-but-broken patch is rejected.

Commit range (optional)

Known-goodKnown-bad

SHAs, tags or branches. Leave both blank to search the last 30 commits up to HEAD.