[Perf] Windows/x64: 1 Regression on 7/29/2026 9:07:05 AM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [7e07d48faae88ae9068a6afc91e7524b2112c0e7](https://github.com/dotnet/sdk/commit/7e07d48faae88ae9068a6afc91e7524b2112c0e7)
Compare | [d2b524965e50619e8db62ed35943981830e1008d](https://github.com/dotnet/sdk/commit/d2b524965e50619e8db62ed35943981830e1008d)
Diff | [Diff](https://github.com/dotnet/sdk/compare/7e07d48faae88ae9068a6afc91e7524b2112c0e7...d2b524965e50619e8db62ed35943981830e1008d)
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
py .\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)

Start by running the provided benchmarks_ci.py command for SixLabors.ImageSharp.Benchmarks.Codecs.Jpeg.DecodeJpeg, then inspect src/benchmarks/real-world/ImageSharp/Codecs/Jpeg/DecodeJpeg.cs and the linked test report. Compare the baseline and test commits and use the profiling or benchmarking workflow docs to investigate the 14% slowdown. Done means the regression is explained and the benchmark no longer shows the reported performance loss.

Written by the indexing model from the issue text.