perf: Prevent redundant calls to getRelevantDataMask #30883
Merged
+41
−24
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.
SUMMARY
Move
getRelevantDataMask
andgetAllActiveFilters
calls from Dashboard'smapStateToProps
to a selector.On a very large dashboard (300+ charts, 40+ filters) those calls delayed the dashboard loading time by over 3 seconds. After this change, they are negligible. Please keep in mind that you likely won't reproduce that delay on a dashboard from sample data, it only occurs on very large ones.
Sidenote - my key takeaway from this is that we really need to optimize our redux selectors with
createSelector
from redux toolkit more often. Plenty of our selectors have quite complex code that is mostly running unnecessarily.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before - you can see that there's a 3.2s load event task, which really consists of thousands of
getRelevantDataMask
calls:After - 0.8ms:
TESTING INSTRUCTIONS
Dashboards with native filters should work just like before
ADDITIONAL INFORMATION