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.
TL;DR;
filterDOMProps
is twice as fast now!This PR optimizes
filterDOMProps
. The benchmark I created consisted of two parts: one where 70%-100% of props were removed and the other where only 0%-20% were removed. Based on one of our apps, an average % of removed props is ~76%.Additionally, the new version results in a smaller bundle as no lodash functions are used.
And finally, I rearranged the code a little to make sure that it'll appear as
filterDOMProps
instead offilter
in error and profiler traces.921ms + 394ms = 1315ms
606ms + 166ms = 772ms
602ms + 47ms = 649ms
552ms + 40ms = 592ms
Benchmarks