dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/8/2026 9:46:51 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 | [aedf05ae4b6c7f74f789e64a0a8d9d169414f04f](https://github.com/dotnet/sdk/commit/aedf05ae4b6c7f74f789e64a0a8d9d169414f04f)
Compare | [10d231dd86555cc17a757c800d821ad8e0f459d5](https://github.com/dotnet/sdk/commit/10d231dd86555cc17a757c800d821ad8e0f459d5)
Diff | [Diff](https://github.com/dotnet/sdk/compare/aedf05ae4b6c7f74f789e64a0a8d9d169414f04f...10d231dd86555cc17a757c800d821ad8e0f459d5)
Configs | CompilationMode:tiered, RunKind:mlnet
### Regressions in Microsoft.ML.Benchmarks.HashBench
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashScalarString - 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 'Microsoft.ML.Benchmarks.HashBench*'
```
### Microsoft.ML.Benchmarks.HashBench.HashScalarString
#### 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/Microsoft.ML.Benchmarks/HashBench.cs around lines 139-140, then review the linked baseline-to-compare commit diff. Run the provided benchmarks_ci.py command and inspect the HashScalarString test report; done means reproducing the slowdown and identifying its cause or an appropriate fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, ubuntu
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100