fix: Memory leak in watch mode and use Set for performance #130
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.
TLDR
Before: 200ms per rebuild (and an additional 200ms for each additional rebuild)
After: ~5ms per rebuild!
The Long Version
Hi! Thanks for the awesome plugin! It has saved my life on many projects. One of my coworkers today was experiencing slow rebuilds in watch mode, and with a little bit of profiling, it turns out this plugin was the culprit. There are 2 issues:
O(n)
_.includes
call that can be replaced with anO(1)
Set.prototype.has
call.Here are the performance characteristics of this patch. The project in question is private, but has 1800 files. The
did it
line is how long this plugin takes to complete:Before Fixing Memory Leak
After Fixing Memory Leak
After Fixing Memory Leak + Switching to Set()
Let me know if you have any questions. Thanks!