dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 3 Improvements on 9/1/2026 4:58:28 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 | [a1d60271d589de52ba513a8265a9038da9eaba5c](https://github.com/dotnet/sdk/commit/a1d60271d589de52ba513a8265a9038da9eaba5c)
Compare | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a1d60271d589de52ba513a8265a9038da9eaba5c...f8a811758057986566da27d06d8f03a7e5e226bf)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Improvements in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Contact4 - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [Contact4Nonconvex - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![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.Contact4
#### ETL Files
#### Histogram
#### JIT Disasms
### DemoBenchmarks.TwoBodyConstraintBenchmarks.Contact4Nonconvex
#### 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 | [a1d60271d589de52ba513a8265a9038da9eaba5c](https://github.com/dotnet/sdk/commit/a1d60271d589de52ba513a8265a9038da9eaba5c)
Compare | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a1d60271d589de52ba513a8265a9038da9eaba5c...f8a811758057986566da27d06d8f03a7e5e226bf)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Improvements in DemoBenchmarks.GatherScatterBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [GatherState - 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.GatherScatterBenchmarks*'
```
### DemoBenchmarks.GatherScatterBenchmarks.GatherState
#### 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 and GatherScatterBenchmarks.cs, then review the linked baseline and comparison commits. Run benchmarks_ci.py with the filters provided and inspect the linked test reports. Done means the reported benchmark changes are reproduced and their cause or required follow-up is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, ubuntu
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100