dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 3 Improvements on 8/24/2026 11:05:53 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 | [51874e577c504e758a38f19bfb9999aa1ad0594a](https://github.com/dotnet/runtime/commit/51874e577c504e758a38f19bfb9999aa1ad0594a)
Compare | [df846d69e1666f9c6060f2487975b568f3ed93bb](https://github.com/dotnet/runtime/commit/df846d69e1666f9c6060f2487975b568f3ed93bb)
Diff | [Diff](https://github.com/dotnet/runtime/compare/51874e577c504e758a38f19bfb9999aa1ad0594a...df846d69e1666f9c6060f2487975b568f3ed93bb)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in System.Collections.CtorFromCollection<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ConcurrentDictionary - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [OrderedDictionary - Duration of single invocation]()
- [ADX - Test Multi Config Graph]()
![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.CtorFromCollection*'
```
### System.Collections.CtorFromCollection<String>.ConcurrentDictionary(Size: 512)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.CtorFromCollection<String>.OrderedDictionary(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)
---
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [51874e577c504e758a38f19bfb9999aa1ad0594a](https://github.com/dotnet/runtime/commit/51874e577c504e758a38f19bfb9999aa1ad0594a)
Compare | [df846d69e1666f9c6060f2487975b568f3ed93bb](https://github.com/dotnet/runtime/commit/df846d69e1666f9c6060f2487975b568f3ed93bb)
Diff | [Diff](https://github.com/dotnet/runtime/compare/51874e577c504e758a38f19bfb9999aa1ad0594a...df846d69e1666f9c6060f2487975b568f3ed93bb)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in Microsoft.Extensions.Logging.Formatting
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [NoArguments - 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 'Microsoft.Extensions.Logging.Formatting*'
```
### Microsoft.Extensions.Logging.Formatting.NoArguments
#### 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 sources at src/benchmarks/micro/libraries/System.Collections/Create/CtorFromCollection.cs and src/benchmarks/micro/libraries/Microsoft.Extensions.Logging/LogValuesBenchmarks.cs, then run the provided benchmarks_ci.py filters. Compare the linked baseline and test reports to determine whether the reported improvements need investigation or a follow-up change; the issue does not specify a code change or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100