dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 8 Regressions on 9/3/2026 9:59:06 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [334cc5c43dfb4b6acab5052c15ee8b1631d069bc](https://github.com/dotnet/runtime/commit/334cc5c43dfb4b6acab5052c15ee8b1631d069bc)
Compare | [134de00ac5934568c582a35322ae16a228db430d](https://github.com/dotnet/runtime/commit/134de00ac5934568c582a35322ae16a228db430d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/334cc5c43dfb4b6acab5052c15ee8b1631d069bc...134de00ac5934568c582a35322ae16a228db430d)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in Exceptions.Handling
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ThrowAndCatch_ManyCatchBlocks - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatchWhenFinally - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatchDeep - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatchWhen - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatch_ManyCatchBlocks - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [TryAndFinallyDeep - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatchDeep - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ThrowAndCatch - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
![graph]()
![graph]()
![graph]()
![graph]()
![graph]()
![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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Exceptions.Handling*'
```
### Exceptions.Handling.ThrowAndCatch_ManyCatchBlocks(kind: ReflectionSoftware)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatchWhenFinally(kind: Software)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatchDeep(kind: Software)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatchWhen(kind: Software)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatch_ManyCatchBlocks(kind: Software)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.TryAndFinallyDeep(kind: Hardware)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatchDeep(kind: Hardware)
#### ETL Files
#### Histogram
#### JIT Disasms
### Exceptions.Handling.ThrowAndCatch(kind: Software)
#### 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 source at src/benchmarks/micro/runtime/Exceptions/Handling.cs, especially the listed ranges for ThrowAndCatch, TryAndFinally, and related benchmarks. Compare the baseline and test commits using the provided links and review the benchmark history and graphs. The issue does not define a specific fix or completion condition beyond investigating the reported regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100