dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 2/19/2026 10:08:45 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 | [0b60d265d30d96c827b73dbce74cb78f600d3c92](https://github.com/dotnet/sdk/commit/0b60d265d30d96c827b73dbce74cb78f600d3c92)
Compare | [181f8798913e9c234e19756db58f38a8cac176ea](https://github.com/dotnet/sdk/commit/181f8798913e9c234e19756db58f38a8cac176ea)
Diff | [Diff](https://github.com/dotnet/sdk/compare/0b60d265d30d96c827b73dbce74cb78f600d3c92...181f8798913e9c234e19756db58f38a8cac176ea)
Configs | CompilationMode:tiered, RunKind:imagesharp
### Improvements in SixLabors.ImageSharp.Benchmarks.Processing.Rotate
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [DoRotate - 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 'SixLabors.ImageSharp.Benchmarks.Processing.Rotate*'
```
### SixLabors.ImageSharp.Benchmarks.Processing.Rotate.DoRotate
#### 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
The payload points to src/benchmarks/real-world/ImageSharp/Processing/Rotate.cs and scripts/benchmarks_ci.py. Start by running the documented benchmarks_ci.py command and reviewing the linked test report. The issue records an automated performance improvement but names no code change or acceptance criterion, so completion cannot be determined from the issue alone.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100