Optimize JSON.dump argument parsing #616
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.
JSON.dump
looks terrible on micro-benchmarks because the way it handles arguments is quite allocation heavy compared to the actual JSON generation work.Profiling the
small hash
benchmarked show 14% of time spent inArray#compact
and34%
time spent inJSON::Ext::GeneratorState.new
. Only41%
in the actualgenerate
function.By micro-optimizing
JSON.dump
, it can look much better:Before:
After:
Now profiles of the
small hash
benchmark show 44% ingenerate
and45%
inGeneratorState
allocation.