dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 5/9/2026 7:00:45 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 | [6b1231dfc6422ae67c7c75371b79ba21d499ba3b](https://github.com/dotnet/runtime/commit/6b1231dfc6422ae67c7c75371b79ba21d499ba3b)
Compare | [c701e381728c5e2cac9e8e8298b9d8921d6f751d](https://github.com/dotnet/runtime/commit/c701e381728c5e2cac9e8e8298b9d8921d6f751d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/6b1231dfc6422ae67c7c75371b79ba21d499ba3b...c701e381728c5e2cac9e8e8298b9d8921d6f751d)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.Tests.Perf_PriorityQueue<String, String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [K_Max_Elements - 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.Tests.Perf_PriorityQueue*'
```
### System.Collections.Tests.Perf_PriorityQueue<String, String>.K_Max_Elements(Size: 10)
#### 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/PriorityQueue/Perf_PriorityQueue.cs#L85-L108 and reproduce the reported System.Collections.Tests.Perf_PriorityQueue result using the provided benchmarks_ci.py command. Compare the baseline and test commits, then investigate the source of the K_Max_Elements regression. Done means the regression is explained and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100