dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/16/2026 12:17:32 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 | [6276bd4a23e9e21597ccccba91f908917bc8e189](https://github.com/dotnet/runtime/commit/6276bd4a23e9e21597ccccba91f908917bc8e189)
Compare | [86f11fbddc7d604daa7296cd9cc8e82211c55c61](https://github.com/dotnet/runtime/commit/86f11fbddc7d604daa7296cd9cc8e82211c55c61)
Diff | [Diff](https://github.com/dotnet/runtime/compare/6276bd4a23e9e21597ccccba91f908917bc8e189...86f11fbddc7d604daa7296cd9cc8e82211c55c61)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Numerics.Tests.Perf_BigInteger
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Divide - 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.Numerics.Tests.Perf_BigInteger*'
```
### System.Numerics.Tests.Perf_BigInteger.Divide(arguments: 16,8 bits)
#### 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 src/benchmarks/micro/libraries/System.Runtime.Numerics/Perf.BigInteger.cs around the Divide benchmark and run the documented benchmarks_ci.py command for System.Numerics.Tests.Perf_BigInteger. Compare the baseline and test commits and review the linked test report to identify the source of the WASM AOT slowdown. Done means the regression is explained and the benchmark no longer shows the reported performance loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100