dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 4/26/2026 8:48:58 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 | [ab01524bbb2ef1eea0ffaef161b3ef5686e8f256](https://github.com/dotnet/sdk/commit/ab01524bbb2ef1eea0ffaef161b3ef5686e8f256)
Compare | [472c68a4fb23be92717d1714fb7a38bda7c4aac0](https://github.com/dotnet/sdk/commit/472c68a4fb23be92717d1714fb7a38bda7c4aac0)
Diff | [Diff](https://github.com/dotnet/sdk/compare/ab01524bbb2ef1eea0ffaef161b3ef5686e8f256...472c68a4fb23be92717d1714fb7a38bda7c4aac0)
Configs | CompilationMode:tiered, RunKind:mlnet
### Improvements 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
Start with the linked HashBench.cs lines 173-174 and run the provided benchmarks_ci.py command using the Microsoft.ML.Benchmarks.HashBench filter. Compare HashVectorFloat with the linked baseline and test reports; done requires a confirmed result and a clearly identified performance change or follow-up.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100