dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/25/2026 5:23: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 | [df846d69e1666f9c6060f2487975b568f3ed93bb](https://github.com/dotnet/runtime/commit/df846d69e1666f9c6060f2487975b568f3ed93bb)
Compare | [cd254340926a9de135f596224d5d4daff12c2395](https://github.com/dotnet/runtime/commit/cd254340926a9de135f596224d5d4daff12c2395)
Diff | [Diff](https://github.com/dotnet/runtime/compare/df846d69e1666f9c6060f2487975b568f3ed93bb...cd254340926a9de135f596224d5d4daff12c2395)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.ContainsTrue<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ImmutableList - 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.ContainsTrue*'
```
### System.Collections.ContainsTrue<String>.ImmutableList(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 linked ContainsTrue.cs benchmark and the baseline/compare commits, then run the documented benchmarks_ci.py command for the System.Collections.ContainsTrue filter. Use the linked test report and performance graph to investigate the regression; done means the cause is identified and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100