Archives

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.

How CedarRecon's exception classifier went from 1,368ms to 646ms per million transactions, and the four optimizations that made things worse before it got better.