dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 8/2/2026 11:04:49 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 | [a2f953fe266dc72602436e77614a9e10f60a7128](https://github.com/dotnet/runtime/commit/a2f953fe266dc72602436e77614a9e10f60a7128)
Compare | [abcd6eb3137ac133ef7f73eae95e7928160386c9](https://github.com/dotnet/runtime/commit/abcd6eb3137ac133ef7f73eae95e7928160386c9)
Diff | [Diff](https://github.com/dotnet/runtime/compare/a2f953fe266dc72602436e77614a9e10f60a7128...abcd6eb3137ac133ef7f73eae95e7928160386c9)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Tests.Perf_Random
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [NextBytes - 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.Tests.Perf_Random*'
```
### System.Tests.Perf_Random.NextBytes
#### 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 benchmark source in performance/src/benchmarks/micro/libraries/System.Runtime.Extensions/Perf.Random.cs at lines 43-44 and the linked NextBytes history report. Run the provided benchmarks_ci.py command, then compare the baseline and regression commits and use the profiling workflow linked in the issue. Done means the x86 Windows NextBytes regression is explained and the measured performance returns to the baseline without introducing another regression.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100