dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Improvement on 7/19/2026 7:43:11 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 | ubuntu 22.04
Queue | AmpereUbuntu
Baseline | [13c03a4a9a854291f77636b1e15038e65919e68b](https://github.com/dotnet/runtime/commit/13c03a4a9a854291f77636b1e15038e65919e68b)
Compare | [cb301bc23e682da023cf3c51985d45fbb528e7c3](https://github.com/dotnet/runtime/commit/cb301bc23e682da023cf3c51985d45fbb528e7c3)
Diff | [Diff](https://github.com/dotnet/runtime/compare/13c03a4a9a854291f77636b1e15038e65919e68b...cb301bc23e682da023cf3c51985d45fbb528e7c3)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in PerfLabTests.DelegatePerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [MulticastDelegateCombineInvoke - 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.DelegatePerf*'
```
### PerfLabTests.DelegatePerf.MulticastDelegateCombineInvoke
#### 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/micro/runtime/perflab/DelegatePerf.cs, especially lines 61-92, then review the linked performance report and baseline/compare commits. Run the provided benchmarks_ci.py command to reproduce the arm64 result. The payload does not identify a requested code change or acceptance test, so completion would require triage to determine whether the measured improvement needs follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, python, ubuntu
- Domain
- operating-systems, performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100