dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 9/5/2026 3:40:05 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 | [b5f06b0847863033c479487e1abe17d30a9a9ab7](https://github.com/dotnet/runtime/commit/b5f06b0847863033c479487e1abe17d30a9a9ab7)
Compare | [967fac9fa69c45f691f809e94c7cb68de6c9cdb1](https://github.com/dotnet/runtime/commit/967fac9fa69c45f691f809e94c7cb68de6c9cdb1)
Diff | [Diff](https://github.com/dotnet/runtime/compare/b5f06b0847863033c479487e1abe17d30a9a9ab7...967fac9fa69c45f691f809e94c7cb68de6c9cdb1)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in System.Tests.Perf_Type
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [GetType_FullyQualifiedNames - 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.Tests.Perf_Type*'
```
### System.Tests.Perf_Type.GetType_FullyQualifiedNames(input: typeof(System.Tests.NestedGeneric<String, Boolean>))
#### 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 in src/benchmarks/micro/libraries/System.Runtime/Perf.Type.cs around lines 55-57, then run the provided benchmarks_ci.py command filtered to System.Tests.Perf_Type. Compare the linked benchmark history and report to determine whether the GetType_FullyQualifiedNames improvement is reproducible and actionable; done means the result has a clear triage outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100