BenchmarkDotNet gives you excellent performance measurements — but no opinion on whether a number is acceptable, no memory of yesterday's baseline, and no way to fail a build. Here's the gap, and what I'm building to close it.
You add [MemoryDiagnoser] and [Benchmark] to a class, run dotnet run -c
Release, and BenchmarkDotNet hands you back a beautifully formatted table:
mean, median, standard deviation, allocated bytes per operation. It's one of
the best measurement tools in any ecosystem.
And then what?
Leaderboard scores don’t hold up when we look more closely at benchmarks that are considered standards. The models dramatically…
Benchmarking is hard. Done wrong it is very misleading, and unfortunately it is frequently done wrong. Let's explore how not to…
Transparent database benchmarks help customers make better decisions and push vendors to build better products.
Benchmarks report averages over fixed test sets. Production failures live in the variance and the tails. Those are two different…
Originally published on PrepStack. Cross-posting the TL;DR here. We run a multi-tenant analytics...
My serverless benchmark prints 0.88 vs 0.3025 — real measurements running on editorial weights. Every index has a committee; the…
