dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/29/2026 10:20:31 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 | [398b6c5d572103decd5cfec64121384bcffc01bc](https://github.com/dotnet/runtime/commit/398b6c5d572103decd5cfec64121384bcffc01bc)
Compare | [5b11923ecac20a8367b4ca60a9b9739479319e9a](https://github.com/dotnet/runtime/commit/5b11923ecac20a8367b4ca60a9b9739479319e9a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/398b6c5d572103decd5cfec64121384bcffc01bc...5b11923ecac20a8367b4ca60a9b9739479319e9a)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Memory.Span<Char>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SequenceEqual - 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>.SequenceEqual(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.Span.SequenceEqual benchmark in src/benchmarks/micro/libraries/System.Memory/Span.cs at lines 62-63, then run the provided benchmarks_ci.py command and inspect the linked test report. The issue records an automated improvement, so a maintainer-defined follow-up is needed before completion can be judged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100