dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 6/21/2026 2:47:11 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [e556d5a7e0e7f3682eea7ce544b29c6f6c75a216](https://github.com/dotnet/runtime/commit/e556d5a7e0e7f3682eea7ce544b29c6f6c75a216)
Compare | [06b80b7dccace56abf56e91e72ee26c2a682b76e](https://github.com/dotnet/runtime/commit/06b80b7dccace56abf56e91e72ee26c2a682b76e)
Diff | [Diff](https://github.com/dotnet/runtime/compare/e556d5a7e0e7f3682eea7ce544b29c6f6c75a216...06b80b7dccace56abf56e91e72ee26c2a682b76e)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.IO.Compression.ZLib
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Compress - Duration of single invocation]()
- [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 'System.IO.Compression.ZLib*'
```
### System.IO.Compression.ZLib.Compress(level: Fastest, file: "sum")
#### 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 System.IO.Compression.ZLib.Compress benchmark and run scripts/benchmarks_ci.py using the documented command and filter. Compare the baseline and test commits and review the linked performance report; done means the regression's cause is identified and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- 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