dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/26/2026 3:50:07 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 | [9f18a550aaa91ecd032ac024b67e03559df9e766](https://github.com/dotnet/runtime/commit/9f18a550aaa91ecd032ac024b67e03559df9e766)
Compare | [7c217acdb9e9fd656a8eba55eb99e52b00300fd3](https://github.com/dotnet/runtime/commit/7c217acdb9e9fd656a8eba55eb99e52b00300fd3)
Diff | [Diff](https://github.com/dotnet/runtime/compare/9f18a550aaa91ecd032ac024b67e03559df9e766...7c217acdb9e9fd656a8eba55eb99e52b00300fd3)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Collections.IterateFor<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [IList - 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.Collections.IterateFor*'
```
### System.Collections.IterateFor<String>.IList(Size: 512)
#### 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/libraries/System.Collections/Iterate/IterateFor.cs#L90-L92 and read the benchmarking workflow documentation. Run the provided benchmarks_ci.py command for System.Collections.IterateFor, then compare the reported baseline and test results; done means the improvement is reproduced and its cause or appropriate follow-up is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, ubuntu, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100