dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 9/3/2026 2:40:37 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [147c024e64965dd98d68ed8419e4f5320852e8ca](https://github.com/dotnet/sdk/commit/147c024e64965dd98d68ed8419e4f5320852e8ca)
Compare | [1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d](https://github.com/dotnet/sdk/commit/1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d)
Diff | [Diff](https://github.com/dotnet/sdk/compare/147c024e64965dd98d68ed8419e4f5320852e8ca...1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashVectorFloat - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Microsoft.ML.Benchmarks.HashBench*'
```
### Microsoft.ML.Benchmarks.HashBench.HashVectorFloat
#### 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
Reproduce the reported result with scripts/benchmarks_ci.py using the Microsoft.ML.Benchmarks.HashBench filter, then inspect src/benchmarks/real-world/Microsoft.ML.Benchmarks/HashBench.cs at lines 173-174. Compare the baseline and test commits and use the linked report or profiling workflow to identify the cause. Done means the Windows/x64 HashVectorFloat regression is understood and no longer reproduces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100