[release/6.0] Remove usage of [AggressiveOptimization] #58253
Merged
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 #58209 to release/6.0
/cc @stephentoub @steveharter
Customer Impact
Removing the usages of
[AggressiveOptimization]
is suggested per the JIT team. It has the potential to increase performance especially when R2R code is not used and PGO (Profile Guided Optimization) kicks in after many runs.Testing
Local benchmarks show that when enabling PGO features (DOTNET_ReadyToRun=0, DOTNET_TC_QuickJitForLoops=1, DOTNET_TieredPGO=1) show up to 10% improvement in a serializer overhead benchmark.
Risk
The expected perf gains are expected to outweigh any possible minor perf regressions; performance will be determined by the jitter and environment settings and not influenced by
[AggressiveOptimization]
.