Repository navigation
Add 1.0.0-based core and middleware benchmark baseline - #50
Merged
Merged
Conversation
This was referenced Oct 18, 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
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.
Adds a standalone .NET 10 BenchmarkDotNet harness on the exact TaskFlow 1.0.0 release commit
0800af84229d7beb3a6fa507d236d0ff533b0c92. The head branchbenchmarks-1.0.0has one benchmark commit directly on that release; the production library, root build configuration, and solution are unchanged.The 16 release-compatible cases cover synchronous/asynchronous completion, caller-token variants, drained bursts, gated enqueue-only submissions, concurrent producers, and pipeline middleware (which already exists in 1.0.0). Keyed scheduling and bounded admission are excluded here because those APIs were introduced later.
PR #47 merges this branch and current
main, reuses the common harness files unchanged, and adds seven cases for the newer APIs. Both PRs targetmain; this release-based PR should be merged first. Check outbenchmarks-1.0.0to measure the unchanged release, andissue-43-benchmarksto measure the current library. Merging this PR intomainadds benchmark infrastructure; reproducing 1.0.0 measurements still requires checking out the release-based branch.The workflow explicitly checks out the PR head SHA and records it in its readable job summary, so release measurements cannot accidentally use GitHub's synthetic merge with current main. The harness remains outside standard solution tests and package publication. Generated reports are available through job summaries/artifacts rather than committed samples. The README documents the branch relationship, a common-case filter, methodology, and the history/comparison follow-ups.
Validation: .NET 10 Release build with zero warnings/errors; all 16 cases validated twice and all 16 executed successfully through BenchmarkDotNet Dry; benchmark whitespace and file-scoped namespace checks passed. A measured burst sample also completed with three warmups and eight actual iterations, with valid statistics and 1,000-operation normalization. Generated data remains outside source control. Verified that the common harness files are byte-identical to PR #47, the workflow summary renders all five report tables using the checked-out SHA, and production files match
0800af8.Part of #43 (parent #42). The remaining newer-API coverage is in #47.