dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/arm64: 1 Improvement on 9/13/2026 9:08:44 AM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | arm64
OS | Windows 10.0.22621
Queue | Pixel
Baseline | [798449390515fa02f4b20160bedc5e34f8fbdfb9](https://github.com/dotnet/runtime/commit/798449390515fa02f4b20160bedc5e34f8fbdfb9)
Compare | [6ed2ba318dcaa936da60f7d6bc9eb30cad54fc0c](https://github.com/dotnet/runtime/commit/6ed2ba318dcaa936da60f7d6bc9eb30cad54fc0c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/798449390515fa02f4b20160bedc5e34f8fbdfb9...6ed2ba318dcaa936da60f7d6bc9eb30cad54fc0c)
Configs | CodeGenType:JIT, CompilationMode:tiered, LinkingType:static, RunKind:android_scenarios, RuntimeType:coreclr
### Improvements in SOD - Android HelloWorld Extracted Size
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SOD - Android HelloWorld Extracted Size - pub\assets\System.IO.Compression.dll]()
- [ADX - Test Multi Config 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 'SOD - Android HelloWorld Extracted Size*'
```
### SOD - Android HelloWorld Extracted Size
#### 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 Test Report and the SOD - Android HelloWorld Extracted Size benchmark, then run the provided benchmarks_ci.py command from the dotnet/performance repository. Trace the 1.01 extracted-size result through the referenced runtime commits and performance workflow documentation. Done means identifying and validating the cause of the measurement change, with supporting benchmark results.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100