dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/10/2026 5:38:55 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 | [ab094c18ba7f4a96d145afd8b34f965c5c3ef31d](https://github.com/dotnet/runtime/commit/ab094c18ba7f4a96d145afd8b34f965c5c3ef31d)
Compare | [c12540eb53044276c55a86c3a834c662eff2872f](https://github.com/dotnet/runtime/commit/c12540eb53044276c55a86c3a834c662eff2872f)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ab094c18ba7f4a96d145afd8b34f965c5c3ef31d...c12540eb53044276c55a86c3a834c662eff2872f)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Memory.Span<Char>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CopyToSame - 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<Char>.CopyToSame(Size: 3000)
#### 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#L47-L48 and the linked performance report for System.Memory.Span.CopyToSame(Size: 3000). Reproduce it with scripts/benchmarks_ci.py using the provided filter and review the profiling and benchmarking workflow docs; the issue does not specify a code change or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, ubuntu, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100