dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 9/1/2026 5:28:08 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [ef3efe5e020e412e4f6453781d59443e975010a4](https://github.com/dotnet/runtime/commit/ef3efe5e020e412e4f6453781d59443e975010a4)
Compare | [818ad35699cf9b1a3e3f2067c133d8dbe599da2e](https://github.com/dotnet/runtime/commit/818ad35699cf9b1a3e3f2067c133d8dbe599da2e)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ef3efe5e020e412e4f6453781d59443e975010a4...818ad35699cf9b1a3e3f2067c133d8dbe599da2e)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in BenchmarksGame.PiDigits_3
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [RunBench - 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 'BenchmarksGame.PiDigits_3*'
```
### BenchmarksGame.PiDigits_3.RunBench(n: 3000, expected: "8649423196\t:3000")
#### 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 by reading the benchmark source at src/benchmarks/micro/runtime/BenchmarksGame/pidigits-3.cs lines 139-142 and the benchmarking workflow documentation. Run the provided benchmarks_ci.py command for BenchmarksGame.PiDigits_3, then compare the linked report and baseline/test results to determine what changed. Done means the improvement is explained and any resulting change is verified by the benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100