dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/31/2026 11:35:06 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 | [640b326fc81d94d410753b67c0f89b166d6666df](https://github.com/dotnet/runtime/commit/640b326fc81d94d410753b67c0f89b166d6666df)
Compare | [44687f2d763be239ff562b137360ab572f47066e](https://github.com/dotnet/runtime/commit/44687f2d763be239ff562b137360ab572f47066e)
Diff | [Diff](https://github.com/dotnet/runtime/compare/640b326fc81d94d410753b67c0f89b166d6666df...44687f2d763be239ff562b137360ab572f47066e)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Collections.RemoveTrue<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Dictionary - 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.RemoveTrue*'
```
### System.Collections.RemoveTrue<Int32>.Dictionary(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 src/benchmarks/micro/libraries/System.Collections/Remove/RemoveTrue.cs at lines 54-66 and reproduce the reported benchmark using scripts/benchmarks_ci.py with the supplied filter. Compare the baseline and test commits, then use the profiling and benchmarking workflow documentation to isolate the regression; done means identifying and addressing the cause and confirming the benchmark no longer regresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, 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
- 35/100