dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Improvements on 7/29/2026 2:44:38 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 | [00fc09ea5b2e39c46d56fda130b6693e07d449d8](https://github.com/dotnet/runtime/commit/00fc09ea5b2e39c46d56fda130b6693e07d449d8)
Compare | [0a25043f48f83ecfa896966929f25f792463344b](https://github.com/dotnet/runtime/commit/0a25043f48f83ecfa896966929f25f792463344b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/00fc09ea5b2e39c46d56fda130b6693e07d449d8...0a25043f48f83ecfa896966929f25f792463344b)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in System.Collections.CreateAddAndClear<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ICollection - 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>.ICollection(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 | [975877333c98d9d08bad66670d74accc6047be34](https://github.com/dotnet/runtime/commit/975877333c98d9d08bad66670d74accc6047be34)
Compare | [0a25043f48f83ecfa896966929f25f792463344b](https://github.com/dotnet/runtime/commit/0a25043f48f83ecfa896966929f25f792463344b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/975877333c98d9d08bad66670d74accc6047be34...0a25043f48f83ecfa896966929f25f792463344b)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements 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: 1000)
#### 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 sources src/benchmarks/micro/libraries/System.Collections/CreateAddAndClear.cs and src/benchmarks/micro/libraries/System.Collections/PriorityQueue/Perf_PriorityQueue.cs, then read the linked benchmarking workflow. Reproduce the reported benchmarks with scripts/benchmarks_ci.py and compare the supplied reports; the issue provides no implementation target or acceptance criterion, so triage must establish what follow-up is needed before work can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100