dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/7/2026 1:25:29 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 | [f2c93f81b35ddc48dd5ad22c759821277db6dfdf](https://github.com/dotnet/sdk/commit/f2c93f81b35ddc48dd5ad22c759821277db6dfdf)
Compare | [a67d575054ff3bcb905ea6699734d0ed8816aa2b](https://github.com/dotnet/sdk/commit/a67d575054ff3bcb905ea6699734d0ed8816aa2b)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f2c93f81b35ddc48dd5ad22c759821277db6dfdf...a67d575054ff3bcb905ea6699734d0ed8816aa2b)
Configs | CompilationMode:tiered, RunKind:imagesharp
### Regressions in SixLabors.ImageSharp.Benchmarks.Codecs.Jpeg.DecodeJpeg
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [JpegBaselineInterleaved444 - 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.Codecs.Jpeg.DecodeJpeg*'
```
### SixLabors.ImageSharp.Benchmarks.Codecs.Jpeg.DecodeJpeg.JpegBaselineInterleaved444
#### 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/real-world/ImageSharp/Codecs/Jpeg/DecodeJpeg.cs, especially the JpegBaselineInterleaved444 benchmark, and run the provided benchmarks_ci.py command from the performance repository. Compare the result with the linked baseline and test commits and use the profiling workflow links for investigation. Done means the reported JPEG benchmark regression is resolved and the result is validated against the comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 35/100