dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 7/6/2026 12:45: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 | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [8f365c934088b8ae21a4dfce8073da0d3eb22a54](https://github.com/dotnet/runtime/commit/8f365c934088b8ae21a4dfce8073da0d3eb22a54)
Compare | [d720474264849c4dafe6e28dc5bd679b4ddbe5fe](https://github.com/dotnet/runtime/commit/d720474264849c4dafe6e28dc5bd679b4ddbe5fe)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8f365c934088b8ae21a4dfce8073da0d3eb22a54...d720474264849c4dafe6e28dc5bd679b4ddbe5fe)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Globalization.Tests.StringEquality
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Compare_Same_Upper - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Globalization.Tests.StringEquality*'
```
### System.Globalization.Tests.StringEquality.Compare_Same_Upper(Count: 1024, Options: (en-US, OrdinalIgnoreCase))
#### 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.Globalization/StringEquality.cs at the Compare_Same_Upper benchmark and run the provided benchmarks_ci.py command. Compare the reported baseline and test results, then use the linked test report and profiling workflow to determine whether the observed improvement requires a runtime change; done means the cause and any justified follow-up are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100