dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 9/4/2026 2:43:47 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 | [25f20c2fd360fc0d7c126e50f7c784f8338d6faf](https://github.com/dotnet/runtime/commit/25f20c2fd360fc0d7c126e50f7c784f8338d6faf)
Compare | [7e807becb8c6b1917dac0565c674ade7947a8bec](https://github.com/dotnet/runtime/commit/7e807becb8c6b1917dac0565c674ade7947a8bec)
Diff | [Diff](https://github.com/dotnet/runtime/compare/25f20c2fd360fc0d7c126e50f7c784f8338d6faf...7e807becb8c6b1917dac0565c674ade7947a8bec)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Buffers.Tests.ReadOnlySequenceTests<Byte>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [IterateTryGetTenSegments - 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 'System.Buffers.Tests.ReadOnlySequenceTests*'
```
### System.Buffers.Tests.ReadOnlySequenceTests<Byte>.IterateTryGetTenSegments
#### 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/micro/libraries/System.Buffers/ReadOnlySequenceTests.cs, especially IterateTryGetTenSegments, and review the baseline-to-compare commit diff. Run the provided benchmarks_ci.py command and inspect the linked test report; done means the x86 Windows regression is explained and a verified correction or disposition is recorded.
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
- 38/100