dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/23/2026 1:41:19 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 | [026096b77a9dcfe0368a5d04d6fdc28efc3865d1](https://github.com/dotnet/runtime/commit/026096b77a9dcfe0368a5d04d6fdc28efc3865d1)
Compare | [54549c8df1cdbd7b373b56a53104439e75bcfcbd](https://github.com/dotnet/runtime/commit/54549c8df1cdbd7b373b56a53104439e75bcfcbd)
Diff | [Diff](https://github.com/dotnet/runtime/compare/026096b77a9dcfe0368a5d04d6fdc28efc3865d1...54549c8df1cdbd7b373b56a53104439e75bcfcbd)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Collections.IndexerSet<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Array - 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.IndexerSet*'
```
### System.Collections.IndexerSet<String>.Array(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 System.Collections.IndexerSet.Array(Size: 512) benchmark source in the linked dotnet/performance file and reproduce it with the provided benchmarks_ci.py command. Compare the baseline and comparison commits, then inspect the linked test report and IR or profiling artifacts. Done means identifying and addressing the cause of the reported 1.19x regression, with the benchmark no longer showing the regression.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100