dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 5/30/2026 9:11: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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [c2bf1a1c93c92918d8c8f7a9f46e2f6f6d432401](https://github.com/dotnet/sdk/commit/c2bf1a1c93c92918d8c8f7a9f46e2f6f6d432401)
Compare | [1616fce88662817fb8b76911fb188b56650859a0](https://github.com/dotnet/sdk/commit/1616fce88662817fb8b76911fb188b56650859a0)
Diff | [Diff](https://github.com/dotnet/sdk/compare/c2bf1a1c93c92918d8c8f7a9f46e2f6f6d432401...1616fce88662817fb8b76911fb188b56650859a0)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashVectorString - 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.HashVectorString
#### 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 167-168 and compare the linked baseline and test runs for HashVectorString. Run the provided benchmarks_ci.py command with the Microsoft.ML.Benchmarks.HashBench* filter, then investigate the regression and verify that the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100