Open performanceautofiler[bot] opened 1 month ago
System.Tests.Perf_String.IndexerCheckLengthHoisting is only seen on Viper AMD64 Windows machines. The rest look like noise. Compare range: https://github.com/dotnet/runtime/compare/e60db076d7966c18b678378b188e6ce6896403d6...fd99ad5002b45a45c3dde9a0260bb6bdd4a88c2f
Another likely related Windows AMD64 Viper only regression at a slightly different time: https://github.com/dotnet/perf-autofiling-issues/issues/39465
Look again at the IndexerCheckLengthHoisting. It is weird that it is only occuring on Windows AMD64 Viper machines.
Run Information
Regressions in Loops.StrengthReduction
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in PerfLabTests.LowLevelPerf
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in SciMark2.kernel
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in Benchstone.BenchI.BenchE
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Run Information
Regressions in System.Tests.Perf_String
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md