dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 2 Regressions on 8/21/2026 2:45:13 AM +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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [be1c680101458a735200e68a74460919be249315](https://github.com/dotnet/runtime/commit/be1c680101458a735200e68a74460919be249315)
Compare | [76c60b960a2daa412c44a5061abf66f3286f6a92](https://github.com/dotnet/runtime/commit/76c60b960a2daa412c44a5061abf66f3286f6a92)
Diff | [Diff](https://github.com/dotnet/runtime/compare/be1c680101458a735200e68a74460919be249315...76c60b960a2daa412c44a5061abf66f3286f6a92)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Memory.Span<Byte>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SequenceCompareTo - 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.Memory.Span*'
```
### System.Memory.Span<Byte>.SequenceCompareTo(Size: 3000)
#### 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [be1c680101458a735200e68a74460919be249315](https://github.com/dotnet/runtime/commit/be1c680101458a735200e68a74460919be249315)
Compare | [76c60b960a2daa412c44a5061abf66f3286f6a92](https://github.com/dotnet/runtime/commit/76c60b960a2daa412c44a5061abf66f3286f6a92)
Diff | [Diff](https://github.com/dotnet/runtime/compare/be1c680101458a735200e68a74460919be249315...76c60b960a2daa412c44a5061abf66f3286f6a92)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Text.Json.Tests.Perf_Base64
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [WriteByteArrayAsBase64_NoEscaping - 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.Text.Json.Tests.Perf_Base64*'
```
### System.Text.Json.Tests.Perf_Base64.WriteByteArrayAsBase64_NoEscaping(NumberOfBytes: 100)
#### 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 the linked benchmark sources, src/benchmarks/micro/libraries/System.Memory/Span.cs and src/benchmarks/micro/libraries/System.Text.Json/Utf8JsonWriter/Perf.Base64.cs, then run the two supplied benchmarks on Windows/x64. Compare the baseline and test commits and inspect the performance reports; done means identifying the cause of both regressions and confirming the affected benchmarks no longer regress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100