dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Regressions on 8/18/2026 1:25:03 PM +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 | [19bc97f3dd3ab67c7810e4ab179125b7c6a60641](https://github.com/dotnet/sdk/commit/19bc97f3dd3ab67c7810e4ab179125b7c6a60641)
Compare | [b8c18a5c2f5d06efdd635120822953728b21678e](https://github.com/dotnet/sdk/commit/b8c18a5c2f5d06efdd635120822953728b21678e)
Diff | [Diff](https://github.com/dotnet/sdk/compare/19bc97f3dd3ab67c7810e4ab179125b7c6a60641...b8c18a5c2f5d06efdd635120822953728b21678e)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Regressions in DemoBenchmarks.GroupedCollisionTesterBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CheapCollisionBenchmarks - 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.GroupedCollisionTesterBenchmarks*'
```
### DemoBenchmarks.GroupedCollisionTesterBenchmarks.CheapCollisionBenchmarks
#### 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)
---
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [19bc97f3dd3ab67c7810e4ab179125b7c6a60641](https://github.com/dotnet/sdk/commit/19bc97f3dd3ab67c7810e4ab179125b7c6a60641)
Compare | [b8c18a5c2f5d06efdd635120822953728b21678e](https://github.com/dotnet/sdk/commit/b8c18a5c2f5d06efdd635120822953728b21678e)
Diff | [Diff](https://github.com/dotnet/sdk/compare/19bc97f3dd3ab67c7810e4ab179125b7c6a60641...b8c18a5c2f5d06efdd635120822953728b21678e)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [BallSocket - 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.BallSocket
#### 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/GroupedCollisionTesterBenchmarks.cs and TwoBodyConstraintBenchmarks.cs, then run the supplied benchmarks_ci.py commands on Ubuntu. Compare the reported results with the baseline and compare commits, using the linked reports and profiling workflow docs for investigation. Done means the cause is identified and reruns show whether the two regressions are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, python, ubuntu
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100