dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 6/24/2026 8:46:56 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [e3cbc00cd3e0b511ad36dc240010eb2b9eefc3b7](https://github.com/dotnet/runtime/commit/e3cbc00cd3e0b511ad36dc240010eb2b9eefc3b7)
Compare | [cd27dcec16016aa54be6a09962d1b509150cf99b](https://github.com/dotnet/runtime/commit/cd27dcec16016aa54be6a09962d1b509150cf99b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/e3cbc00cd3e0b511ad36dc240010eb2b9eefc3b7...cd27dcec16016aa54be6a09962d1b509150cf99b)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in Benchstone.BenchI.Ackermann
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Test - 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 'Benchstone.BenchI.Ackermann*'
```
### Benchstone.BenchI.Ackermann.Test
#### 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/runtime/Benchstones/BenchI/Ackermann.cs and run the supplied benchmarks_ci.py command to reproduce the Ackermann result. The report does not specify a code change or acceptance condition, so completion would require triage to identify an actionable cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100