Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add benchmarks for Utf8JsonReader.Get* #1381
Add benchmarks for Utf8JsonReader.Get* #1381
Changes from all commits
f229919
dc83ab7
8f1b2bb
cfa56f9
b663b52
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jozkee do you know what part of the total time is spent for the creation of
Utf8JsonReader
, callingRead
and callingGetByte()
? What is the typical usage ofreader.GetX()
methods?I am asking because the creation of the reader and call to
reader.Read
might be more expensive than the call toGetX
which we are trying to measure here. If this is true, we should reconsider rewriting the benchmark to something like:this should allow for removal of
UseLargeValue
and hence reducing the number of new benchmarks and the time it takes to run them by half. Please see https://github.com/dotnet/performance/blob/master/docs/microbenchmark-design-guidelines.md#Test-Cases for moreThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, for
GetInt32
, ~80% time is spent in the first two lines:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW I added
ReadToEnd*
benchmarks in order to measure how much time is spent in traversing the 100 elements of the json.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another approach that we could take to avoid having the
ReadtoEnd*
methods could be just callreader.GetInt32()
over the same token a hundred times, that could remove the overhead ofreader.Read()
.