dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 9/9/2026 6:49:16 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 | [da9fcf3d9033b0eb2a277a60fb3239e53b849adb](https://github.com/dotnet/runtime/commit/da9fcf3d9033b0eb2a277a60fb3239e53b849adb)
Compare | [c35a46ec58817a320d41fbb64abfd4ac176cb53b](https://github.com/dotnet/runtime/commit/c35a46ec58817a320d41fbb64abfd4ac176cb53b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/da9fcf3d9033b0eb2a277a60fb3239e53b849adb...c35a46ec58817a320d41fbb64abfd4ac176cb53b)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.ContainsTrueComparer<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ImmutableSortedSet - 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.ContainsTrueComparer*'
```
### System.Collections.ContainsTrueComparer<String>.ImmutableSortedSet(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/Contains/ContainsTrueComparer.cs and compare the baseline and test commits linked in the issue. Run the provided benchmarks_ci.py command, then inspect the linked test report and performance graph to identify the regression; done means the cause is understood and the benchmark no longer regresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100