dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/23/2026 11:09:33 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [ae899ea0758628a22feb37a1401ae397cc5fc8d1](https://github.com/dotnet/sdk/commit/ae899ea0758628a22feb37a1401ae397cc5fc8d1)
Compare | [4f6d02131fae05b5de421f33e38dc73906ef5aca](https://github.com/dotnet/sdk/commit/4f6d02131fae05b5de421f33e38dc73906ef5aca)
Diff | [Diff](https://github.com/dotnet/sdk/compare/ae899ea0758628a22feb37a1401ae397cc5fc8d1...4f6d02131fae05b5de421f33e38dc73906ef5aca)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashVectorKey - 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.HashVectorKey
#### 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 at lines 186-187 and reproduce using the provided benchmarks_ci.py command. Compare the listed baseline and test commits on Windows x64, then investigate the HashVectorKey duration regression. Done means identifying and addressing the cause so the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100