dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/22/2026 4:13:56 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [a4b2df0e43b45c9a5ecb638bf0bb92ebef9234f0](https://github.com/dotnet/runtime/commit/a4b2df0e43b45c9a5ecb638bf0bb92ebef9234f0)
Compare | [026096b77a9dcfe0368a5d04d6fdc28efc3865d1](https://github.com/dotnet/runtime/commit/026096b77a9dcfe0368a5d04d6fdc28efc3865d1)
Diff | [Diff](https://github.com/dotnet/runtime/compare/a4b2df0e43b45c9a5ecb638bf0bb92ebef9234f0...026096b77a9dcfe0368a5d04d6fdc28efc3865d1)
Configs | CompilationMode:wasm, RunKind:micro
### Regressions in System.Memory.Span<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Clear - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Memory.Span*'
```
### System.Memory.Span<Int32>.Clear(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 linked regression report and the benchmark source at src/benchmarks/micro/libraries/System.Memory/Span.cs. Compare the baseline and test commits, reproduce the System.Memory.Span.Clear(Size: 512) benchmark with the provided benchmarks_ci.py command, and use the profiling workflow docs to investigate the 7% regression. Done means identifying and addressing the cause, then confirming the benchmark no longer regresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100