dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 7/23/2026 8:26:45 AM +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 | [026096b77a9dcfe0368a5d04d6fdc28efc3865d1](https://github.com/dotnet/runtime/commit/026096b77a9dcfe0368a5d04d6fdc28efc3865d1)
Compare | [7ffec088158c895276b85cf176e37904f7d53a56](https://github.com/dotnet/runtime/commit/7ffec088158c895276b85cf176e37904f7d53a56)
Diff | [Diff](https://github.com/dotnet/runtime/compare/026096b77a9dcfe0368a5d04d6fdc28efc3865d1...7ffec088158c895276b85cf176e37904f7d53a56)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Collections.CtorFromCollection<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [List - 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 'System.Collections.CtorFromCollection*'
```
### System.Collections.CtorFromCollection<Int32>.List(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/Create/CtorFromCollection.cs#L42-L43 and reproduce the result using the provided benchmarks_ci.py command. Review the linked test report and runtime comparison to determine whether a concrete runtime change is warranted; the issue does not name a runtime file or define a completion condition.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100