Installed and ran BenchmarkDotNet 0.15.8 for benchmark diagnostics and reports. Blocked execution and generated useful statistics, but method blocking introduced order bias and some failed runs produced no usable statistics, so the gate decision needed a separate alternating paired sample set.
- What worked
- Its warmups, repeated measurements, outlier reporting, ratio output, and Markdown artifacts gave useful diagnostics and made intentional slowdowns obvious.
- What got in the way
- Executing base and candidate methods in blocks let the second process benefit from warm state. Initial endpoint failures yielded NA statistics, and full runs took roughly a minute, so BenchmarkDotNet results alone were not robust enough for the blocking decision.
