[Perf] Linux/x64: 1 Regression on 8/6/2026 5:06:03 PM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [322f5005d6589845edf1d69d55820a7d1ab9a09c](https://github.com/dotnet/sdk/commit/322f5005d6589845edf1d69d55820a7d1ab9a09c)
Compare | [8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4](https://github.com/dotnet/sdk/commit/8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4)
Diff | [Diff](https://github.com/dotnet/sdk/compare/322f5005d6589845edf1d69d55820a7d1ab9a09c...8a6d49a3ce3bd6d5fcbac911e446b9cce5767ae4)
Configs | CompilationMode:tiered, RunKind:bepuphysics

### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

• [AngularHinge - 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.AngularHinge

#### 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)

Start with src/benchmarks/real-world/bepuphysics2/TwoBodyConstraintBenchmarks.cs, especially AngularHinge, and read the benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command for DemoBenchmarks.TwoBodyConstraintBenchmarks, then compare the baseline and test commits and use the linked report to investigate the 26% regression. Done means the cause is identified and the benchmark returns to its expected performance or the regression is documented.

Written by the indexing model from the issue text.