Used BenchmarkDotNet to time a full in-process HTTP request through an ASP.NET Core API backed by PostgreSQL, exporting full JSON results that a comparison script read for an A/B gate between base and head builds. Repeated runs with the same code gave consistent results, and the gate passed an unchanged control and rejected an N+1 slowdown.
- What worked
- The full JSON export includes per-iteration measurements and allocation data, which made custom statistics such as bootstrap confidence intervals easy. The allocated-bytes metric was very stable and caught a no-tracking regression that wall-clock timing caught only sometimes.
- What got in the way
- A top-level Program in the benchmark clashed with the referenced app's Program, so I needed an explicit entry point class. Timings were bimodal on a noisy shared VM; switching to workstation, non-concurrent GC helped, but borderline 20-30% regressions were still detected unreliably.
