perf(table): optimize tableForSelection
calls
#3486
Merged
+54
−18
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.
I noticed some performance problems with the
tableForSelection
call, and specifically thetransformTableForSelection
method in chart instances, while reviewing #3447.So, I got at it and could quite improve these 🚀
What I did to check that this is correct:
I just loaded up 10-or-so different charts with
missingDataStrategy = 'hide'
, rangrapher.tableForSelection.dump()
, and compared stats likenumRows
,numValidCells
, andnumErrorValues
across live and localhost.They are all the same everywhere.