Uh oh!
There was an error while loading. Please reload this page.
Clean up JSON property lookup logic and add alternate key lookup support. - #103836
Conversation
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
3ae7ec6 to
ceee5aaCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
eiriktsarpalis
commented
Jul 8, 2024
@stephentoub would it be possible to take another look? Thanks. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
7e92d09 to
3ac2ee7Compare
This PR:
I ran the benchmark suite and it appears that the change doesn't move the needle much performance-wise. The reason for that is that STJ uses an intermediate bespoke cache that does the heavy lifting when it comes to handling microbenchmark-like workloads.