Regressions in System.Threading.Tasks.Tests.Perf_AsyncMethods

[performanceautofiler]

Run Information

Name	Value
Architecture	x64
OS	ubuntu 22.04
Queue	TigerUbuntu
Baseline	44a5abd54c8c6888cdbb7fac490279fd7ee3334e
Compare	920cd6e2b01d0fbede8882d015329e9b4d448c98
Diff	Diff
Configs	CompilationMode:tiered, RunKind:micro

Regressions in System.Threading.Tasks.Tests.Perf_AsyncMethods

Benchmark	Baseline	Test	Test/Base	Test Quality	Edge Detector	Baseline IR	Compare IR	IR Ratio
Yield - Duration of single invocation 📝 - Benchmark Source 📈 - ADX Test Multi Config Graph	313.35 ns	336.14 ns	1.07	0.04	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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Threading.Tasks.Tests.Perf_AsyncMethods*'

Payloads

Baseline
Compare

System.Threading.Tasks.Tests.Perf_AsyncMethods.Yield

ETL Files

Histogram

JIT Disasms

Docs

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

[cincuranet]

The diff is roughly 44a5abd...848c729. Could #87672 be the reason? cc @kouvel

[kouvel]

It seems unlikely to me that #87672 could cause it, the Lock type is not used by anything in coreclr currently and the remaining changes in the PR were only minor changes that don't appear to be perf-related.