Closed performanceautofiler[bot] closed 2 weeks ago
Tagging subscribers to this area: @dotnet/area-system-runtime See info in area-owners.md if you want to be subscribed.
The commit range in question really only has bug fixes. There's nothing obvious that causes these regressions and they are all on the order of 4-40ns.
@AaronRobinsonMSFT, could these be caused by https://github.com/dotnet/runtime/pull/106497, that looks like the most obvious one in the commit range given what the tests are doing (often touching GetType()
).
Yes, it is entirely possible. There was a minor accepted performance regression in that PR. The benefit is the removal of Helper Method Frames and was thus permitted. Given the very small impact here, nanoseconds, this seems acceptable.
Closing as by design.
Run Information
Regressions in System.Tests.Perf_Enum
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in Microsoft.Extensions.DependencyInjection.GetService
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in Microsoft.Extensions.DependencyInjection.GetServiceIEnumerable
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in System.ComponentModel.Tests.Perf_TypeDescriptorTests
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md