dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 2/27/2026 9:07:45 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [0b60d265d30d96c827b73dbce74cb78f600d3c92](https://github.com/dotnet/sdk/commit/0b60d265d30d96c827b73dbce74cb78f600d3c92)
Compare | [181f8798913e9c234e19756db58f38a8cac176ea](https://github.com/dotnet/sdk/commit/181f8798913e9c234e19756db58f38a8cac176ea)
Diff | [Diff](https://github.com/dotnet/sdk/compare/0b60d265d30d96c827b73dbce74cb78f600d3c92...181f8798913e9c234e19756db58f38a8cac176ea)
Configs | CompilationMode:tiered, RunKind:mlnet
### Improvements in Microsoft.ML.Benchmarks.KMeansAndLogisticRegressionBench
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [TrainKMeansAndLR - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Microsoft.ML.Benchmarks.KMeansAndLogisticRegressionBench*'
```
### Microsoft.ML.Benchmarks.KMeansAndLogisticRegressionBench.TrainKMeansAndLR
#### 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 benchmark source at src/benchmarks/real-world/Microsoft.ML.Benchmarks/KMeansAndLogisticRegressionbench.cs#L24-L53 and reproduce it using scripts/benchmarks_ci.py with the provided filter. Compare the reported baseline and test results with the linked history and report. The issue does not define a code change or completion criteria, so triage must establish what, if anything, should be changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- machine-learning, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100