Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance: Websocket: Client -> Server: Big size, causes excecution / reruns to slow down #283

Open
robingie opened this issue Jun 26, 2024 · 0 comments

Comments

@robingie
Copy link

I noticed, that the binary message sizes through the web socket massively increase when displaying more than 500 rows.
Once the grid result is loaded and rendered, it's pushed through the web socket with every rerun.

Unfortunately, that causes laggy reruns due to size when working with a slower connection or higher latency. Placing widgets under the grid doesn't work well because the execution sometimes stops.

Is there a way to reduce the transmitted size and transmit only the delta changes like Streamlit is already doing natively with their st.dataframe / st.data_editor widget?

image

@robingie robingie changed the title Websocket: Client -> Server: Big size, causes excecution / reruns to slow down Performance: Websocket: Client -> Server: Big size, causes excecution / reruns to slow down Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant