dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 6/29/2026 9:44:34 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x64
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [f5a9853b34aeeec46e5729715a62ef2095607f13](https://github.com/dotnet/runtime/commit/f5a9853b34aeeec46e5729715a62ef2095607f13)
Compare | [8b16f838b402a42d4edd4d6ed299ed2d4508a2a2](https://github.com/dotnet/runtime/commit/8b16f838b402a42d4edd4d6ed299ed2d4508a2a2)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f5a9853b34aeeec46e5729715a62ef2095607f13...8b16f838b402a42d4edd4d6ed299ed2d4508a2a2)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Threading.Tests.Perf_Lock
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ReaderWriterLockSlimPerf - 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.Threading.Tests.Perf_Lock*'
```
### System.Threading.Tests.Perf_Lock.ReaderWriterLockSlimPerf
#### 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.Threading.Tests.Perf_Lock benchmark source in performance/src/benchmarks/micro/libraries/System.Threading/Perf.Lock.cs, then run the provided benchmarks_ci.py command. Review the linked test report and baseline/compare data to determine whether the ReaderWriterLockSlimPerf improvement is reproducible and actionable; the issue does not define a code change or explicit completion criteria.
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
- Needs clarification
- Newbie friendliness
- 28/100