dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/21/2026 4:33:08 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 | [1fb02ff55d2046e7e46b89467235f92e39d2099f](https://github.com/dotnet/runtime/commit/1fb02ff55d2046e7e46b89467235f92e39d2099f)
Compare | [f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1](https://github.com/dotnet/runtime/commit/f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1)
Diff | [Diff](https://github.com/dotnet/runtime/compare/1fb02ff55d2046e7e46b89467235f92e39d2099f...f9b6d584afa7ac1f655c5e9d991b6f9eea1052d1)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Memory.Memory<Char>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ToArray - 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.Memory*'
```
### System.Memory.Memory<Char>.ToArray(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 System.Memory.Memory.ToArray(Size: 512) benchmark in performance/src/benchmarks/micro/libraries/System.Memory/Memory.cs and compare the linked baseline and test commits. Run the provided benchmarks_ci.py command and inspect the linked test report or profiling workflow to identify the regression. Done means the benchmark no longer shows the reported regression on Linux/x64 WebAssembly AOT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100