Improve performance of 3D scenes by sending multiple messages at once #3017
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.
This PR experiments with sending all non-update messages at once to reduce the time for creating complex 3D scenes like discussed in #3009.
A demo with 10,000 boxes still takes a while:
I'm not sure if sending tens of thousands of messages at once is a good idea or if we should create chunks. And it is unclear what the remaining bottleneck is. Should we optimize the Python code, the payload or the JavaScript code on the client? Maybe combining multiple steps for creating a 3D object (8 at the moment) into one function call would also be a reasonable improvement.