dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression 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 | [69d18c7af02f97ed5588f06adb0f63491c1b2be1](https://github.com/dotnet/runtime/commit/69d18c7af02f97ed5588f06adb0f63491c1b2be1)
Compare | [0a25043f48f83ecfa896966929f25f792463344b](https://github.com/dotnet/runtime/commit/0a25043f48f83ecfa896966929f25f792463344b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/69d18c7af02f97ed5588f06adb0f63491c1b2be1...0a25043f48f83ecfa896966929f25f792463344b)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions 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 and the linked test report, then reproduce it with the provided benchmarks_ci.py command. Compare the listed baseline and test commits and use the profiling and benchmarking workflow docs; done requires identifying and addressing the reported performance regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100