dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Improvements on 7/28/2026 2:40:15 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 | [00115f085a2df36ea7b135673d290298e20775f7](https://github.com/dotnet/runtime/commit/00115f085a2df36ea7b135673d290298e20775f7)
Compare | [975877333c98d9d08bad66670d74accc6047be34](https://github.com/dotnet/runtime/commit/975877333c98d9d08bad66670d74accc6047be34)
Diff | [Diff](https://github.com/dotnet/runtime/compare/00115f085a2df36ea7b135673d290298e20775f7...975877333c98d9d08bad66670d74accc6047be34)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in MicroBenchmarks.Serializers.Json_FromString<MyEventsListerViewModel>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SystemTextJson_Reflection_ - 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 'MicroBenchmarks.Serializers.Json_FromString*'
```
### MicroBenchmarks.Serializers.Json_FromString<MyEventsListerViewModel>.SystemTextJson_Reflection_
#### 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 | [00115f085a2df36ea7b135673d290298e20775f7](https://github.com/dotnet/runtime/commit/00115f085a2df36ea7b135673d290298e20775f7)
Compare | [975877333c98d9d08bad66670d74accc6047be34](https://github.com/dotnet/runtime/commit/975877333c98d9d08bad66670d74accc6047be34)
Diff | [Diff](https://github.com/dotnet/runtime/compare/00115f085a2df36ea7b135673d290298e20775f7...975877333c98d9d08bad66670d74accc6047be34)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in System.Text.Json.Serialization.Tests.ReadJson<StructRecord>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [DeserializeFromUtf8Bytes - 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.Text.Json.Serialization.Tests.ReadJson*'
```
### System.Text.Json.Serialization.Tests.ReadJson<StructRecord>.DeserializeFromUtf8Bytes(Mode: Reflection)
#### 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/Serializers/Json_FromString.cs and src/benchmarks/micro/libraries/System.Text.Json/Serializer/ReadJson.cs, then run the listed benchmarks_ci.py filters using the benchmarking workflow documentation. Compare the reported baseline and test results to investigate the two improvements; the issue provides no requested code change or completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100