Repository navigation
[release/11.0] Add AggressiveOptimization to key long-running async methods - #69293
Merged
Merged
Conversation
github-actions
Bot
requested review from
BrennanConroy,
SamMonoRT and
halter73
as code owners
September 14, 2026 17:47
BrennanConroy
added
the
Servicing-consider
Contributor
|
Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
artl93
added
Servicing-approved
SamMonoRT
approved these changes
Sep 14, 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.
Backport of #69287 to release/11.0
/cc @BrennanConroy @jakobbotsch
Add AggressiveOptimization to key long-running async methods
Description
Adds
AggressiveOptimizationto a few methods that have shown to hit issues with runtime-async and OSR not playing nicely in 11.0. This helps improve some perf regressions and there is a follow-up issue filed to enhance runtime-async and OSR for 12.0 dotnet/runtime#133672Customer Impact
Improved performance.
Regression?
Regressed when runtime-async was enabled by default
Risk
No functional code changes, just changing how the compiler optimizes a couple methods
Verification
Packaging changes reviewed?