dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/18/2026 1:36:35 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 | [19bc97f3dd3ab67c7810e4ab179125b7c6a60641](https://github.com/dotnet/sdk/commit/19bc97f3dd3ab67c7810e4ab179125b7c6a60641)
Compare | [b8c18a5c2f5d06efdd635120822953728b21678e](https://github.com/dotnet/sdk/commit/b8c18a5c2f5d06efdd635120822953728b21678e)
Diff | [Diff](https://github.com/dotnet/sdk/compare/19bc97f3dd3ab67c7810e4ab179125b7c6a60641...b8c18a5c2f5d06efdd635120822953728b21678e)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FuzzyContains_IndexedSet - 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 'Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks.FuzzyContains_IndexedSet
#### 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/real-world/Akade.IndexedSet.Benchmarks/FullTextIndexBenchmarks.cs, especially lines 32-36, and run the provided benchmarks_ci.py command for the FuzzyContains_IndexedSet benchmark. Compare the baseline and test commits and use the linked report and profiling workflow to identify the regression. Done means the cause is understood and the benchmark no longer shows the reported regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, ubuntu
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100