[Perf] Linux/arm64: SciMark2.kernel Regression on 10/15/2024 8:19:02 AM

[performanceautofiler]

Run Information

Name	Value
Architecture	arm64
OS	ubuntu 22.04
Queue	AmpereUbuntu
Baseline	4e2fe8d886e2ca8df51643b7aa69e7ee33cf2296
Compare	69dc5ec395749dc17434140881eb1414fc989c28
Diff	Diff
Configs	CompilationMode:tiered, RunKind:micro

Regressions in SciMark2.kernel

Benchmark	Baseline	Test	Test/Base	Test Quality	Edge Detector	Baseline IR	Compare IR	IR Ratio
benchmarkLU - Duration of single invocation 📝 - Benchmark Source ADX - Test Multi Config Graph	663.96 ms	717.40 ms	1.08	0.01	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 'SciMark2.kernel*'

SciMark2.kernel.benchmarkLU

ETL Files

Histogram

JIT Disasms

Docs

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

[LoopedBard3]

Likely caused by #108771. @AndyAyersMS

Compare range: 0212c3d...8ef27e2

[AndyAyersMS]

Going to wait for x64 results (we previewed and they looked like a mixed bag).

May want to up the limit, but before I do that I'll dig in and see what lead to the regression.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[AndyAyersMS]

ADX shows it's mainly ARM that is impacted (one might guess because there are more registers...?)