dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [cb84c8521ce6a4cbde63cb1a700fcb850be791ae](https://github.com/dotnet/runtime/commit/cb84c8521ce6a4cbde63cb1a700fcb850be791ae)
Compare | [f43516f45fff5920eabd11753bd5f1803cfacd0c](https://github.com/dotnet/runtime/commit/f43516f45fff5920eabd11753bd5f1803cfacd0c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/cb84c8521ce6a4cbde63cb1a700fcb850be791ae...f43516f45fff5920eabd11753bd5f1803cfacd0c)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in LinqBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Where01ForX - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'LinqBenchmarks*'
```
### LinqBenchmarks.Where01ForX
#### 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 LinqBenchmarks.Where01ForX source in performance/src/benchmarks/micro/runtime/Linq/Linq.cs and read the benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command, then compare the reported baseline and test results to determine what needs attention and what result would confirm the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100