Open performanceautofiler[bot] opened 3 weeks ago
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis See info in area-owners.md if you want to be subscribed.
PTAL @etemi
TBH I don't (yet) see how this regression is related to my changes. I will try to reproduce this locally.
Regression for System.Text.Json.Document.Tests.Perf_EnumerateObject.PropertyIndexer(TestCase: StringProperties) seems to be caused by other changes
Regression for System.Text.Json.Document.Tests.Perf_EnumerateObject.PropertyIndexer(TestCase: NumericProperties) seems to be caused by my changes. Unfortunately I wasn't able to reproduce it locally. @eiriktsarpalis Could you please take a look too?
I find it unlikely that this is being caused by #106503. It adds a few instructions to the main JsonDocument
parsing method that could, theoretically, incur regressions in the micro level however the benchmark itself measures enumeration of a pre-parsed document which exercises a completely disjoint code-path.
The regression concerns main
, so I'm updating the milestone to reflect this.
Run Information
Regressions in System.Text.Json.Document.Tests.Perf_EnumerateObject
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md