dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 9/9/2026 10:13:48 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 | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Compare | [c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da](https://github.com/dotnet/sdk/commit/c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f8a811758057986566da27d06d8f03a7e5e226bf...c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SwingLimit - 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 'DemoBenchmarks.TwoBodyConstraintBenchmarks*'
```
### DemoBenchmarks.TwoBodyConstraintBenchmarks.SwingLimit
#### 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/real-world/bepuphysics2/TwoBodyConstraintBenchmarks.cs, especially SwingLimit at lines 136-150, and reproduce it with the provided benchmarks_ci.py command. Compare the baseline and test commits and use the linked report and profiling workflow to investigate the 1.50x regression. Done means the regression is explained and addressed, with the benchmark no longer showing the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, python, ubuntu
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100