dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/10/2026 9:01:08 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 | [65937ca43416615d941a93c9f33ad4b1acfb7b58](https://github.com/dotnet/runtime/commit/65937ca43416615d941a93c9f33ad4b1acfb7b58)
Compare | [25bd04c79542dfaaab5c5cd42670bcfc20b7d57a](https://github.com/dotnet/runtime/commit/25bd04c79542dfaaab5c5cd42670bcfc20b7d57a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/65937ca43416615d941a93c9f33ad4b1acfb7b58...25bd04c79542dfaaab5c5cd42670bcfc20b7d57a)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Span - 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>.Span(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/ContainsTrue.cs#L59-L69 and compare the listed baseline and compare commits. Run the provided benchmarks_ci.py command and inspect the linked test report or profiling workflow; done means the ContainsTrue Span regression is explained and addressed.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100