dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 5/1/2026 9:47:36 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 | [8e7e7589051881332c387c46760773d1caed5712](https://github.com/dotnet/runtime/commit/8e7e7589051881332c387c46760773d1caed5712)
Compare | [b74595701421282895300b139f2064745c583f7d](https://github.com/dotnet/runtime/commit/b74595701421282895300b139f2064745c583f7d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8e7e7589051881332c387c46760773d1caed5712...b74595701421282895300b139f2064745c583f7d)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Collections.Sort<BigStruct>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Array - 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.Collections.Sort*'
```
### System.Collections.Sort<BigStruct>.Array(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.Collections/Sort.cs#L44-L45 and the linked test report for System.Collections.Sort.Array(Size: 512). Run the documented benchmarks_ci.py command, then compare the baseline and test reports to determine whether the reported improvement exposes an actionable runtime change; the issue is done only when triage identifies a concrete next step.
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
- 25/100