dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/14/2026 10:22:33 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 | [d00a0a24912957046ed2443adc0af7bbfb4c43bc](https://github.com/dotnet/runtime/commit/d00a0a24912957046ed2443adc0af7bbfb4c43bc)
Compare | [420dfbb4f584c1b0ddebec9615d1a673437050f6](https://github.com/dotnet/runtime/commit/420dfbb4f584c1b0ddebec9615d1a673437050f6)
Diff | [Diff](https://github.com/dotnet/runtime/compare/d00a0a24912957046ed2443adc0af7bbfb4c43bc...420dfbb4f584c1b0ddebec9615d1a673437050f6)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Collections.CreateAddAndRemove<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Stack - 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.CreateAddAndRemove*'
```
### System.Collections.CreateAddAndRemove<Int32>.Stack(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/CreateAddAndRemove.cs#L131-L144 and review the linked performance report for the wasm AOT run. Reproduce it with scripts/benchmarks_ci.py using the documented filter, then compare the baseline and test results. Done means identifying and addressing the performance improvement after triage, with the benchmark confirming the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100