bench: use more iterations/revisions for the native json_encode baseline #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The function call is very very fast and very little differences will have a large effect on rel. comparision to parsica. Try to make it more stable
staabm
changed the title
|
Merged this squashed with a change that also does this to the other JSON Bench methods. thanks! 🙇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The function call is very very fast and very little differences will have a large effect on rel. comparision to parsica.
Try to make it more stable.
Motivation: in #45 (comment) the benchmark went from 12.533μs (before-mean) to 13.333μs (after-mean) which is a diff of ~ 10% without other modifications