Use BitSet for bundler intersections #8862
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.
↪️ Pull Request
In really large projects, the bundler can spend huge amounts of time performing expensive set intersections. This PR replaces Set's with a custom
BitSet
class implemented withBigInt
when intersections are needed to be performed.The BitSet requires a list of all possible items before individual sets can be made. In the case of the bundler, this is the list of all known assets.
Unfortunately, we don't really see any performance wins on most projects but a large internal project saw a 44 second improvement to dev bundle time.
Bonus change
I upgraded our eslint config to es2020 to add support for BigInts
🚨 Test instructions
Tests added, plus existing bundler tests should be sufficient
✔️ PR Todo