dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/15/2026 9:13:52 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 | [9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2](https://github.com/dotnet/sdk/commit/9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2)
Compare | [ecc427bc7d7b4ee32b943f71196ab377f67c1105](https://github.com/dotnet/sdk/commit/ecc427bc7d7b4ee32b943f71196ab377f67c1105)
Diff | [Diff](https://github.com/dotnet/sdk/compare/9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2...ecc427bc7d7b4ee32b943f71196ab377f67c1105)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashVectorDouble - 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.HashVectorDouble
#### 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, especially HashVectorDouble around lines 180-181, and compare the baseline and test commits listed in the report. Run the provided benchmarks_ci.py command on Ubuntu 22.04 and inspect the linked history and performance report. Done means the regression is explained and the benchmark returns to the expected performance, with validation recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100