-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Improve perf for internal map/filter ops #5126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
size-limit report 📦
|
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d02a7dd:
|
✅ Deploy Preview for redux-starter-kit-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This PR:
getCurrentfrom coreremoveCacheKeyFromTagsto ensure we're filtering plain arrays of tagsinvalidationByTagsmiddlewarehasPendingRequestslogic that iterated over all cache entries, with a simple counter comparisonfilterMaputil that runs both a predicate and a mapper in a single loopfilter().filter().map()flatten()util we had in favor of standard.flatMap()Partial work on #3823 , but a different angle.
Combined, I see some small but meaningful improvements for updates in a many-entries-many-tags scenario, like here:
Before:
After: