dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/19/2026 5:54:44 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 | [2515f972d25ec6ab5868f696273bd02a6275e273](https://github.com/dotnet/runtime/commit/2515f972d25ec6ab5868f696273bd02a6275e273)
Compare | [f43516f45fff5920eabd11753bd5f1803cfacd0c](https://github.com/dotnet/runtime/commit/f43516f45fff5920eabd11753bd5f1803cfacd0c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2515f972d25ec6ab5868f696273bd02a6275e273...f43516f45fff5920eabd11753bd5f1803cfacd0c)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in LinqBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Order00LinqMethodX - 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 'LinqBenchmarks*'
```
### LinqBenchmarks.Order00LinqMethodX
#### 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 src/benchmarks/micro/runtime/Linq/Linq.cs at lines 339-352 and run the provided benchmarks_ci.py command with the LinqBenchmarks filter. Compare the reported baseline and test results, then determine whether the improvement is reproducible and what concrete follow-up is warranted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100