dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/19/2026 2:42:16 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 | [13c03a4a9a854291f77636b1e15038e65919e68b](https://github.com/dotnet/runtime/commit/13c03a4a9a854291f77636b1e15038e65919e68b)
Compare | [2515f972d25ec6ab5868f696273bd02a6275e273](https://github.com/dotnet/runtime/commit/2515f972d25ec6ab5868f696273bd02a6275e273)
Diff | [Diff](https://github.com/dotnet/runtime/compare/13c03a4a9a854291f77636b1e15038e65919e68b...2515f972d25ec6ab5868f696273bd02a6275e273)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### 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 the PerfLabTests.DelegatePerf.MulticastDelegateCombineInvoke benchmark in performance/src/benchmarks/micro/runtime/perflab/DelegatePerf.cs, then read the benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command and compare the baseline and test reports; the issue does not define a specific code change or completion criterion beyond investigating the reported performance result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, python, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100