perf: add BenchmarkDotNet baseline project (#163, #185)#242
Merged
Conversation
Stands up benchmarks/Wolfgang.Etl.Abstractions.Benchmarks measuring the abstraction overhead the library adds over bare in-memory sequences: - ExtractorBenchmarks: ExtractorBase extraction loop, no-progress vs with-progress (Interlocked counter + timer/final-report path). - PipelineBenchmarks: fluent Pipeline builder vs hand-wired IAsyncEnumerable composition vs base-class composition (the builder is documented as zero-extra-allocation sugar; the benchmark verifies it). #185: benchmarks/.editorconfig relaxes the analyzer rules that don't fit a benchmark harness (AsyncFixer01, MA0004, S1215, VSTHRD200), mirroring the ETL-FixedWidth reference. Benchmark components are internal; build clean under Release/TreatWarningsAsErrors. The gh-pages publish workflow (#164) follows in a separate protected-file PR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stands up the BenchmarkDotNet baseline project for ETL-Abstractions.
Closes #163 (BenchmarkDotNet baseline project) and #185 (benchmark
.editorconfig/ TreatWarningsAsErrors). The gh-pages publish workflow (#164) follows as a small protected-file PR (it adds.github/workflows/benchmarks.yaml).What it measures
An abstractions library has no I/O to benchmark, so the project measures the overhead the base classes add over a bare in-memory sequence:
ExtractorBaseextraction loop, no-progress vs with-progress (theInterlockeditem counter + the timer / final-report path).Pipelinebuilder vs hand-wiredIAsyncEnumerablecomposition vs base-class composition. The builder is documented as zero-extra-allocation sugar; the benchmark makes that verifiable (Dry run already shows ~696 B builder vs ~328 B manual).Notes
benchmarks/.editorconfig([Maintenance] performance: Hold benchmark projects to TreatWarningsAsErrors (curated benchmarks/.editorconfig) #185) relaxes the analyzer rules that don't fit a benchmark harness (AsyncFixer01, MA0004, S1215, VSTHRD200).internal; whole-solution Release build is clean under TreatWarningsAsErrors (0 warnings).docfx.yamlalready preservesdev/on gh-pages, so the published chart won't be wiped by doc deploys.Part of: #154