dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 8/10/2026 5:40:28 AM +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 | [c668fd41fd95a3b52c783bfdc761604712010ba3](https://github.com/dotnet/runtime/commit/c668fd41fd95a3b52c783bfdc761604712010ba3)
Compare | [ab094c18ba7f4a96d145afd8b34f965c5c3ef31d](https://github.com/dotnet/runtime/commit/ab094c18ba7f4a96d145afd8b34f965c5c3ef31d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/c668fd41fd95a3b52c783bfdc761604712010ba3...ab094c18ba7f4a96d145afd8b34f965c5c3ef31d)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.IO.Tests.BinaryWriterTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [WriteHalf - 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.Tests.BinaryWriterTests*'
```
### System.IO.Tests.BinaryWriterTests.WriteHalf
#### 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.Tests.BinaryWriterTests.WriteHalf benchmark and the linked test report, then follow the profiling and benchmarking workflow documents. Reproduce it with the provided benchmarks_ci.py command and compare the listed baseline and compare commits. Done means the x86 Windows performance regression is explained and the benchmark no longer shows the reported degradation.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100