dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Improvement on 9/1/2026 5:15:28 PM +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 | ubuntu 22.04
Queue | AmpereUbuntu
Baseline | [bdcba57531224815fbbc0fbb5ee23a1d3876d43a](https://github.com/dotnet/runtime/commit/bdcba57531224815fbbc0fbb5ee23a1d3876d43a)
Compare | [5ea788a76b90b3ce533ec04750817dc703e69208](https://github.com/dotnet/runtime/commit/5ea788a76b90b3ce533ec04750817dc703e69208)
Diff | [Diff](https://github.com/dotnet/runtime/compare/bdcba57531224815fbbc0fbb5ee23a1d3876d43a...5ea788a76b90b3ce533ec04750817dc703e69208)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in PerfLabTests.LowLevelPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [InterfaceInterfaceMethodSwitchCallType - 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 'PerfLabTests.LowLevelPerf*'
```
### PerfLabTests.LowLevelPerf.InterfaceInterfaceMethodSwitchCallType
#### 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 PerfLabTests.LowLevelPerf.InterfaceInterfaceMethodSwitchCallType benchmark in performance/src/benchmarks/micro/runtime/perflab/LowLevelPerf.cs, lines 157-168, and review the linked baseline, comparison, and test reports. Run the provided benchmarks_ci.py command and determine what change is expected; done means the relevant arm64 Ubuntu benchmark result is validated against the reported improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, ubuntu
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100