dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Regression on 8/11/2026 4:34:13 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 | ubuntu 22.04
Queue | AmpereUbuntu
Baseline | [795badfa03d01074a359ce0b65da2213043ee78c](https://github.com/dotnet/runtime/commit/795badfa03d01074a359ce0b65da2213043ee78c)
Compare | [633ab1a41439ad2405ba2eb241295ba1842fcf5a](https://github.com/dotnet/runtime/commit/633ab1a41439ad2405ba2eb241295ba1842fcf5a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/795badfa03d01074a359ce0b65da2213043ee78c...633ab1a41439ad2405ba2eb241295ba1842fcf5a)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.IO.Tests.Perf_Directory
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [RecursiveCreateDeleteDirectory - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.IO.Tests.Perf_Directory*'
```
### System.IO.Tests.Perf_Directory.RecursiveCreateDeleteDirectory(depth: 100)
#### 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 RecursiveCreateDeleteDirectory benchmark in src/benchmarks/micro/libraries/System.IO.FileSystem/Perf.Directory.cs and run the provided benchmarks_ci.py command for System.IO.Tests.Perf_Directory. Compare the baseline and test commits and use the linked test report and profiling workflow docs to identify the regression. Done means the benchmark no longer shows the reported Linux/arm64 slowdown and the relevant performance result is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100