dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 8/10/2026 9:25:30 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 | [8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4](https://github.com/dotnet/sdk/commit/8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4)
Compare | [7fb8cef14d9ae6bd729b04638f88d00f1ba7eb99](https://github.com/dotnet/sdk/commit/7fb8cef14d9ae6bd729b04638f88d00f1ba7eb99)
Diff | [Diff](https://github.com/dotnet/sdk/compare/8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4...7fb8cef14d9ae6bd729b04638f88d00f1ba7eb99)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [HashVectorDouble - 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.HashVectorDouble
#### 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 180-181 and review the linked HashVectorDouble benchmark report. Run the provided benchmarks_ci.py command and compare the Windows/x64 result with the listed baseline and comparison commits. The issue does not define a requested code change, so completion would require identifying an actionable performance fix or confirming that no change is needed.
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
- 28/100