dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/5/2026 8:48:27 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 | [a9679a8de87742e170318ea39f7f0e2874bcd441](https://github.com/dotnet/sdk/commit/a9679a8de87742e170318ea39f7f0e2874bcd441)
Compare | [02385e26e452b21a97d8a5e694fe3ada7259a582](https://github.com/dotnet/sdk/commit/02385e26e452b21a97d8a5e694fe3ada7259a582)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a9679a8de87742e170318ea39f7f0e2874bcd441...02385e26e452b21a97d8a5e694fe3ada7259a582)
Configs | CompilationMode:tiered, RunKind:imagesharp
### Regressions in SixLabors.ImageSharp.Benchmarks.Codecs.DecodeBmp
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [BmpImageSharp - 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.DecodeBmp*'
```
### SixLabors.ImageSharp.Benchmarks.Codecs.DecodeBmp.BmpImageSharp(TestImage: "Bmp/Car.bmp")
#### 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 baseline and compare commits, then follow the benchmarking workflow documentation and reproduce the SixLabors.ImageSharp.Benchmarks.Codecs.DecodeBmp filter using scripts/benchmarks_ci.py. Compare the reported 81.72 μs baseline with the 100.44 μs test result and use the linked benchmark and report pages to identify the regression. Done means the cause is identified and the benchmark no longer shows the reported regression.
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
- 30/100