dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 7/7/2026 1:33:18 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 | [d720474264849c4dafe6e28dc5bd679b4ddbe5fe](https://github.com/dotnet/runtime/commit/d720474264849c4dafe6e28dc5bd679b4ddbe5fe)
Compare | [4245753ead3ca70a287ac1234cd91ce1b782d5a8](https://github.com/dotnet/runtime/commit/4245753ead3ca70a287ac1234cd91ce1b782d5a8)
Diff | [Diff](https://github.com/dotnet/runtime/compare/d720474264849c4dafe6e28dc5bd679b4ddbe5fe...4245753ead3ca70a287ac1234cd91ce1b782d5a8)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Memory.Span<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Fill - 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.Memory.Span*'
```
### System.Memory.Span<Int32>.Fill(Size: 512)
#### 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 at src/benchmarks/micro/libraries/System.Memory/Span.cs lines 53-54 and run the provided benchmarks_ci.py command for System.Memory.Span.Fill. Compare the baseline and test reports linked in the issue, then determine whether the measured improvement needs follow-up or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100