dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 9/1/2026 3:34:53 PM +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 | Mac OS X 10.18
Queue | IPhone
Baseline | [72fa82ba43d9e5171e225027471b51b5abc25d98](https://github.com/dotnet/sdk/commit/72fa82ba43d9e5171e225027471b51b5abc25d98)
Compare | [36ea4de4a4409ace6bdf48c2dae2b6713f47c1b9](https://github.com/dotnet/sdk/commit/36ea4de4a4409ace6bdf48c2dae2b6713f47c1b9)
Diff | [Diff](https://github.com/dotnet/sdk/compare/72fa82ba43d9e5171e225027471b51b5abc25d98...36ea4de4a4409ace6bdf48c2dae2b6713f47c1b9)
Configs | CodeGenType:NativeAOT, CompilationMode:tiered, RunKind:maui_scenarios_ios, RuntimeType:coreclr
### Regressions in Build Time - .NET iOS Default Template
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [NET iOS Default Template - Publish Time]()
- [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 'Build Time - .NET iOS Default Template*'
```
### Build Time - .NET iOS Default Template
#### 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 scripts/benchmarks_ci.py and the benchmarking workflow linked in the issue, using the reported .NET iOS Default Template filter. Compare the baseline and test commits, then inspect the linked test report and performance graph to determine whether the publish-time regression reproduces. Done means identifying the cause and validating the result against this benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- build-system, mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100