When a benchmark regresses, the investigation usually starts in a pull request
comment, and that's exactly where it should end too. Mention @codspeedbot in
any pull request comment, issue comment, or review comment and the
Wizard will analyze your performance data, explain what happened, and propose a
fix directly in GitHub.
Performance breakdown: get a summary of how a branch affects performance before merging.
@codspeedbot what's the performance impact of this PR?
Explain a regression: the Wizard inspects the flamegraph, identifies the root cause, and writes up a plain-language explanation.
@codspeedbot explain the regression on bench_parse
Propose a fix: the Wizard investigates the regression and opens a pull request with a targeted code change.
@codspeedbot fix the regression on bench_serialize
Add benchmarks: request coverage for a specific function or module and the Wizard will write the benchmarks and open a PR.
@codspeedbot add a benchmark for the parse_config function
The CodSpeed GitHub App must be installed on your repository. Then drop a comment in any pull request and let the Wizard take it from there.
Learn more in the Wizard documentation.