dotnet-ci-benchmarking

Automated .NET performance regression detection compares BenchmarkDotNet JSON exports against historical baselines stored as GitHub Actions artifacts. It flags execution time and memory allocation degradation based on configurable percentage thresholds to prevent bad merges.

Set up a GitHub Actions workflow to fail builds on benchmark degradation by running BenchmarkDotNet on every pull request, comparing the JSON output to a baseline artifact, and configuring the build to fail if timing or memory regressions exceed your threshold.

Yes, this CI benchmarking approach requires BenchmarkDotNet v0.14 or higher. It also requires a GitHub Actions runner environment to store baseline artifacts and execute the performance regression testing workflows.

Yes, you can configure custom percentage thresholds for both memory allocation and execution time regressions. The comparison logic evaluates BenchmarkDotNet JSON exports against these thresholds to determine if a performance regression occurred.

The best way to track baseline performance metrics for dotnet benchmarks is to store BenchmarkDotNet JSON exports as GitHub Actions artifacts. This allows automated CI workflows to fetch and compare historical baselines against current runs.

Developers are alerted of performance regressions through generated reports and automated GitHub Actions build failures. The system can also comment directly on pull requests when timing or memory allocation thresholds are breached.