Performance of state diffing: improve runtime type checks #2072
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.
The functions
notebook_to_js
andFirebasey.diff
are performance bottlenecks right now, and their runtime scales linearly with notebook size. They are called after every notebook state change.For the PlutoUI sample notebook, which is quite large, these functions take about 5ms (on a fast CPU), adding a 5ms overhead to any state change.
Before
After