dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 9/1/2026 4:58:26 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [a1d60271d589de52ba513a8265a9038da9eaba5c](https://github.com/dotnet/sdk/commit/a1d60271d589de52ba513a8265a9038da9eaba5c)
Compare | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a1d60271d589de52ba513a8265a9038da9eaba5c...f8a811758057986566da27d06d8f03a7e5e226bf)
Configs | CompilationMode:tiered, RunKind:imagesharp
### Improvements 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)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/benchmarks/real-world/ImageSharp/Codecs/Jpeg/DecodeJpeg.cs at the referenced benchmark lines, then run the supplied benchmarks_ci.py command with the DecodeJpeg filter. Compare the reported baseline and test results and use the linked test report or profiling workflow to investigate; done means the improvement is understood and validated by the benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100