Backend performance: delete stale connections #2977
Merged
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.
After a client disconnects, Pluto continues to calculate and send updates for that client. This can be a performance problem: on every refresh of a notebook, the update logic becomes slower.
This PR fixes that, and removes clients from memory after their websocket disconnects.
This PR also updates the frontend's reconnecting logic. This is currently not implemented (and incorrect: all updates while disconnected are ignored). I replaced it with a call to
reset_shared_state
.TOOD
Reconnecting:
Schermopname.2024-08-05.om.14.29.31.mov