dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Regressions on 7/27/2026 11:29:43 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 | [2aa2ce008a33a25ac77f4f340b628e135b94087f](https://github.com/dotnet/runtime/commit/2aa2ce008a33a25ac77f4f340b628e135b94087f)
Compare | [da6081391e5d3227e462c082b345af8720db05c1](https://github.com/dotnet/runtime/commit/da6081391e5d3227e462c082b345af8720db05c1)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2aa2ce008a33a25ac77f4f340b628e135b94087f...da6081391e5d3227e462c082b345af8720db05c1)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.CreateAddAndClear<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SortedSet - 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.CreateAddAndClear*'
```
### System.Collections.CreateAddAndClear<String>.SortedSet(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)
---
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [2aa2ce008a33a25ac77f4f340b628e135b94087f](https://github.com/dotnet/runtime/commit/2aa2ce008a33a25ac77f4f340b628e135b94087f)
Compare | [da6081391e5d3227e462c082b345af8720db05c1](https://github.com/dotnet/runtime/commit/da6081391e5d3227e462c082b345af8720db05c1)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2aa2ce008a33a25ac77f4f340b628e135b94087f...da6081391e5d3227e462c082b345af8720db05c1)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.Sort<IntClass>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Array_Comparison - 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.Sort*'
```
### System.Collections.Sort<IntClass>.Array_Comparison(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 reported benchmark sources, src/benchmarks/micro/libraries/System.Collections/CreateAddAndClear.cs and Sort.cs, then run the listed benchmarks through performance/scripts/benchmarks_ci.py. Review the baseline and compare links plus the benchmarking and profiling workflow docs. Done means the two regressions are explained and a verified fix or disposition is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, ubuntu, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100