[Perf] Windows/x64: 1 Regression on 4/19/2025 12:13:01 AM +00:00

[performanceautofiler]

Run Information

Name	Value
Architecture	x64
OS	Windows 10.0.22631
Queue	ViperWindows
Baseline	ca451bfcbc2415d2d85f5dc51c6f577011f274f7
Compare	55b8f9fe7b0e3b00d5d1419f64763e141570f206
Diff	Diff
Configs	CompilationMode:tiered, RunKind:micro

Regressions in Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark

Benchmark	Baseline	Test	Test/Base	Test Quality	Edge Detector	Baseline IR	Compare IR	IR Ratio
CreateInstance_1 - Duration of single invocation 📝 - Benchmark Source ADX - Test Multi Config Graph	69.16 ns	93.62 ns	1.35	0.52	False

Test Report

Repro

General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md

git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark*'

Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark.CreateInstance_1

ETL Files

Histogram

JIT Disasms

Docs

Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository

[AndyAyersMS]

Unclear

https://pvscmdupload.z22.web.core.windows.net/autofilereport/autofilereports/04_22_2025/refs/heads/main_x64_Windows%2010.0.22631/ViperWindows_Regression/Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark.html

Possibly dotnet/runtime#114660

[AaronRobinsonMSFT]

I've reverted the performance issues from dotnet/runtime#114660. This can likely be closed.

[LoopedBard3]

Results are back to they were before due to something in range: dotnet/runtime@ab30ec7...09cb359.