You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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?
The text was updated successfully, but these errors were encountered: