dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 9/13/2026 9:28:00 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 | [1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d](https://github.com/dotnet/sdk/commit/1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d)
Compare | [fb92951eceabe91c5015b35e49acdbc9c867aaf8](https://github.com/dotnet/sdk/commit/fb92951eceabe91c5015b35e49acdbc9c867aaf8)
Diff | [Diff](https://github.com/dotnet/sdk/compare/1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d...fb92951eceabe91c5015b35e49acdbc9c867aaf8)
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
The report points to src/benchmarks/real-world/Microsoft.ML.Benchmarks/HashBench.cs at lines 173-174 and the HashVectorFloat benchmark. Start by following the benchmarking workflow and running the provided benchmarks_ci.py command, then compare the reported Windows/x64 result with the linked baseline and test commits. The report does not define a code change or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100