chore: bson/json comparison benchmarks #2799
Merged
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.
I modified the #2974 benchmarks to include the same test but with BSON
encoding.
BSON is faster than JSON in most/many csaes, with much more stable
perofrmance patterns, though tthe larger globs-cases are curious, and
may be a sign that the test hits some larger limitation of the
hardware.
This could be interesting fodder--with tests run other than on my
laptop--for a blog post or similar about enconding impacts on
performance.