dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Regression on 8/26/2026 4:02:35 AM +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 | [519e88bf80b5d39bc2c4e788a025a499136a1661](https://github.com/dotnet/runtime/commit/519e88bf80b5d39bc2c4e788a025a499136a1661)
Compare | [08df03ba6493589f3816e193847b50f105bf4c7a](https://github.com/dotnet/runtime/commit/08df03ba6493589f3816e193847b50f105bf4c7a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/519e88bf80b5d39bc2c4e788a025a499136a1661...08df03ba6493589f3816e193847b50f105bf4c7a)
Configs | CompilationMode:tiered, R2RType:r2r_interpreter, RunKind:micro
### Regressions in Exceptions.Handling
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ThrowAndCatch - 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 'Exceptions.Handling*'
```
### Exceptions.Handling.ThrowAndCatch(kind: ReflectionHardware)
#### 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 Exceptions.Handling.ThrowAndCatch benchmark in dotnet/performance/src/benchmarks/micro/runtime/Exceptions/Handling.cs, then run the documented benchmarks_ci.py command with the Exceptions.Handling filter. Compare the baseline and test commits and profiling or report links to determine the cause of the arm64 Azure Linux regression; done means the regression is explained and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, linux
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100