This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Fix for #21456 (Regressions in attribute allocations for non-generic attributes) #21462
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.
This is a quick-fix for #21456 where regressions between
netcoreapp2.1
andnetcoreapp3.0
were discovered on most attribute pathways due to the allocation overhead in the generic-supporting pathways. This was introduced in #9189 (thanks @jkotas for the quick find). The workaround here is to simply not take that slow/expensive path for non-generics.While I'd like to optimize
RuntimeModule.ResolveMethod
further, there's a public surface area in play there that makes the changes non-trivial. There, we'll have to choose overhead on the public path (which may still be a net win), or duplication in code for another path.Benchmarks are available in
dotnet/performance
- run via:Before (netcoreapp3.0 preview 1 - same as master)
After
cc @jkotas @AviAvni @stephentoub