dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/25/2026 10:54:05 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 | [b756a8d8a0e64905e16c81911bb09a8110bc3395](https://github.com/dotnet/sdk/commit/b756a8d8a0e64905e16c81911bb09a8110bc3395)
Compare | [1d4910780fe728cf5affade170fe51fc8f96f9fb](https://github.com/dotnet/sdk/commit/1d4910780fe728cf5affade170fe51fc8f96f9fb)
Diff | [Diff](https://github.com/dotnet/sdk/compare/b756a8d8a0e64905e16c81911bb09a8110bc3395...1d4910780fe728cf5affade170fe51fc8f96f9fb)
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 the reported SixLabors.ImageSharp.Benchmarks.Codecs.Jpeg.DecodeJpeg benchmark source at src/benchmarks/real-world/ImageSharp/Codecs/Jpeg/DecodeJpeg.cs#L54-L55 and the linked baseline/compare commits. Run the provided benchmarks_ci.py command and review the benchmark report and profiling workflow to identify the regression; done means the cause is understood and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, 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