dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 4/13/2026 11:16:41 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [98d1ffed9caa5d66873c34bc2c9fdd31f41bf6dd](https://github.com/dotnet/runtime/commit/98d1ffed9caa5d66873c34bc2c9fdd31f41bf6dd)
Compare | [60815e7908757660418fb297313fecd4b8c080ac](https://github.com/dotnet/runtime/commit/60815e7908757660418fb297313fecd4b8c080ac)
Diff | [Diff](https://github.com/dotnet/runtime/compare/98d1ffed9caa5d66873c34bc2c9fdd31f41bf6dd...60815e7908757660418fb297313fecd4b8c080ac)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in PerfLabTests.LowLevelPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [GenericGenericMethod - 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.GenericGenericMethod
#### 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 GenericGenericMethod benchmark in src/benchmarks/micro/runtime/perflab/LowLevelPerf.cs around lines 354-363. Run the listed benchmarks_ci.py command using the benchmarking workflow documentation, then compare the reported baseline and test results. Done means determining whether the Linux/x64 improvement is reproducible and whether the report identifies an actionable runtime change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100