dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 9/4/2026 2:43:47 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 | [134de00ac5934568c582a35322ae16a228db430d](https://github.com/dotnet/runtime/commit/134de00ac5934568c582a35322ae16a228db430d)
Compare | [7e807becb8c6b1917dac0565c674ade7947a8bec](https://github.com/dotnet/runtime/commit/7e807becb8c6b1917dac0565c674ade7947a8bec)
Diff | [Diff](https://github.com/dotnet/runtime/compare/134de00ac5934568c582a35322ae16a228db430d...7e807becb8c6b1917dac0565c674ade7947a8bec)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Tests.Perf_Guid
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [EqualsNotSame - 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.Tests.Perf_Guid*'
```
### System.Tests.Perf_Guid.EqualsNotSame
#### 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/Perf.Guid.cs at EqualsNotSame and run the benchmarks_ci.py command from the issue. Review the linked regression and test reports against the baseline and compare commits to determine whether the result is reproducible. Done means the regression is explained and the benchmark result is validated after the appropriate fix or triage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100