dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 8/28/2026 11:31:31 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 | [100da3f94464f99616ee4a401670bec491ebc787](https://github.com/dotnet/runtime/commit/100da3f94464f99616ee4a401670bec491ebc787)
Compare | [aa036afce592ad80e938a35bd376222fb232cba9](https://github.com/dotnet/runtime/commit/aa036afce592ad80e938a35bd376222fb232cba9)
Diff | [Diff](https://github.com/dotnet/runtime/compare/100da3f94464f99616ee4a401670bec491ebc787...aa036afce592ad80e938a35bd376222fb232cba9)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Buffers.Tests.RentReturnArrayPoolTests<Byte>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ProducerConsumer - 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.RentReturnArrayPoolTests*'
```
### System.Buffers.Tests.RentReturnArrayPoolTests<Byte>.ProducerConsumer(RentalSize: 4096, ManipulateArray: False, Async: False, UseSharedPool: True)
#### 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 linked benchmark source in performance/src/benchmarks/micro/libraries/System.Buffers/ArrayPoolTests.cs around lines 106-149, then run the provided benchmarks_ci.py command for the named test. Compare the result with the linked report and determine whether the measured improvement is reproducible and actionable; done means the performance finding has a confirmed explanation or follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100