-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Perf] Regressions in Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable #56781
Comments
Tagging subscribers to this area: @eerhardt, @maryamariyan Issue DetailsRun Information
Regressions in Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable
Reprogit clone https://github.com/dotnet/performance.git
python3 .\performance\scripts\benchmarks_ci.py -f netcoreapp5.0 --filter 'Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable*' PayloadsHistogramMicrosoft.Extensions.DependencyInjection.GetServiceIEnumerable.Transient
DocsProfiling workflow for dotnet/runtime repository
|
@maryamariyan - any way this could have been caused by #56324? |
Using a commit from today's main branch in dotnet/runtime (d329350), runtime/src/libraries/Microsoft.Extensions.DependencyInjection/src/ServiceProvider.cs Line 170 in e5c0b81
to _realizedServices[callSite.ServiceType] = accessor; Improves perf from
to
Steps to get numbers: (following docs page in benchmarking-workflow-dotnet-runtime.md)
Also tried running baseline commit in this issue (fae1412) for the same test and that gives the report below: (not fully building runtime but using DI and DI.Abstractions code snapshot from the baseline commt)
|
Fixed by #57155. |
Run Information
Regressions in Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable
Historical Data in Reporting System
Repro
Payloads
Baseline
Compare
Histogram
Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable.Transient
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: