mediatorlite-benchmarks

You can benchmark MediatorLite against MediatR using a pre-configured BenchmarkDotNet harness that ensures DI parity and standard memory diagnosis settings. This setup eliminates manual configuration errors and produces reproducible performance comparison results.

Measuring .NET mediator library overhead requires running four pre-built benchmark scenarios covering simple request dispatch, stacked pipeline behaviors, and sequential or parallel notification publishing. This approach captures source generator dispatch and pipeline overhead accurately.

DI container configuration affects performance testing by introducing unfair variations if not matched correctly. Using pre-built DI containers for both libraries ensures test parity, while disabling observability prevents skewed, non-representative benchmark results.

Yes, you can validate performance regressions in source-generated dispatch code by running the benchmark suite. The harness applies standard warmup and iteration counts to provide reproducible measurements for .NET library maintenance workflows.

Benchmarking pipeline behaviors and notification publishing covers single pipeline behavior, multiple stacked behaviors, and sequential or parallel notification publishing. These scenarios measure the overhead introduced by MediatorLite and MediatR during request execution.