dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 2 Regressions on 8/25/2026 10:44:15 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | arm64
OS | azurelinux 3.0
Queue | CobaltAzureLinux
Baseline | [8baacb006f5615ebd705bdf9de98ca5df7bf1ba1](https://github.com/dotnet/runtime/commit/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1)
Compare | [9f18a550aaa91ecd032ac024b67e03559df9e766](https://github.com/dotnet/runtime/commit/9f18a550aaa91ecd032ac024b67e03559df9e766)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1...9f18a550aaa91ecd032ac024b67e03559df9e766)
Configs | CompilationMode:tiered, R2RType:r2r_interpreter, RunKind:micro
### Regressions in PerfLabTests.DictionaryExpansion
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ExpandDictionaries - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
[Test Report]()
### Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
```cmd
git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'PerfLabTests.DictionaryExpansion*'
```
### PerfLabTests.DictionaryExpansion.ExpandDictionaries
#### ETL Files
#### Histogram
#### JIT Disasms
### Docs
[Profiling workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/profiling-workflow-dotnet-runtime.md)
[Benchmarking workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md)
---
### Run Information
Name | Value
-- | --
Architecture | arm64
OS | azurelinux 3.0
Queue | CobaltAzureLinux
Baseline | [8baacb006f5615ebd705bdf9de98ca5df7bf1ba1](https://github.com/dotnet/runtime/commit/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1)
Compare | [9f18a550aaa91ecd032ac024b67e03559df9e766](https://github.com/dotnet/runtime/commit/9f18a550aaa91ecd032ac024b67e03559df9e766)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1...9f18a550aaa91ecd032ac024b67e03559df9e766)
Configs | CompilationMode:tiered, R2RType:r2r_interpreter, RunKind:micro
### Regressions in System.Tests.Perf_Decimal
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Parse - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
[Test Report]()
### Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
```cmd
git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Tests.Perf_Decimal*'
```
### System.Tests.Perf_Decimal.Parse(value: "123456.78900000000430736690760")
#### ETL Files
#### Histogram
#### JIT Disasms
### Docs
[Profiling workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/profiling-workflow-dotnet-runtime.md)
[Benchmarking workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the benchmark sources DictionaryExpansion.cs lines 145-151 and Perf.Decimal.cs lines 28-30, then run the provided benchmarks_ci.py commands for each filter. Compare the ARM64 AzureLinux results with the listed baseline and compare commits. Done means the two reported regressions are reproduced, explained, and the resulting benchmark report no longer shows an unexplained regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, linux
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100