dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Improvements on 9/13/2026 3:54:51 AM +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 | [b9678dcc0e7bac74a0d6b669b39d1007359b0016](https://github.com/dotnet/runtime/commit/b9678dcc0e7bac74a0d6b669b39d1007359b0016)
Compare | [3c4631e63b1de4308e2965b149992b992c9f5318](https://github.com/dotnet/runtime/commit/3c4631e63b1de4308e2965b149992b992c9f5318)
Diff | [Diff](https://github.com/dotnet/runtime/compare/b9678dcc0e7bac74a0d6b669b39d1007359b0016...3c4631e63b1de4308e2965b149992b992c9f5318)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements 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)
---
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [b9678dcc0e7bac74a0d6b669b39d1007359b0016](https://github.com/dotnet/runtime/commit/b9678dcc0e7bac74a0d6b669b39d1007359b0016)
Compare | [3c4631e63b1de4308e2965b149992b992c9f5318](https://github.com/dotnet/runtime/commit/3c4631e63b1de4308e2965b149992b992c9f5318)
Diff | [Diff](https://github.com/dotnet/runtime/compare/b9678dcc0e7bac74a0d6b669b39d1007359b0016...3c4631e63b1de4308e2965b149992b992c9f5318)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Text.Json.Node.Tests.Perf_Create
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Create_JsonString - 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.Text.Json.Node.Tests.Perf_Create*'
```
### System.Text.Json.Node.Tests.Perf_Create.Create_JsonString
#### 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 docs/benchmarking-workflow-dotnet-runtime.md and the benchmark sources src/benchmarks/micro/libraries/System.IO.FileSystem/Perf.Directory.cs and src/benchmarks/micro/libraries/System.Text.Json/Node/Perf_Create.cs. Run the two listed benchmarks, then compare their reports with the linked baseline and comparison commits. Done means confirming the reported improvements and determining whether this auto-filed result requires follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100