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
The biggest speed bottleneck and breaking issue is the message queue size. At the moment it's 50 kilobytes. Not all messages (read: web pages) are 50 kb. There are performance advantages to be had by lowering it and things just truncate if you try to display a larger page.
This can be fixed by chunking the messages. I'll need to do some testing for optimal chunk size but instead of sending one large message, a message large enough for most cases with the ability to send additional messages is the solution here.
It would be possible to do it always with two messages from the server to the client: 1. here's the size of the data to expect in message 2. 2. here's the data of the size you're expecting but this will give an unnecessary overhead if it could be done in a single message as it is now.
The text was updated successfully, but these errors were encountered:
The biggest speed bottleneck and breaking issue is the message queue size. At the moment it's 50 kilobytes. Not all messages (read: web pages) are 50 kb. There are performance advantages to be had by lowering it and things just truncate if you try to display a larger page.
This can be fixed by chunking the messages. I'll need to do some testing for optimal chunk size but instead of sending one large message, a message large enough for most cases with the ability to send additional messages is the solution here.
It would be possible to do it always with two messages from the server to the client: 1. here's the size of the data to expect in message 2. 2. here's the data of the size you're expecting but this will give an unnecessary overhead if it could be done in a single message as it is now.
The text was updated successfully, but these errors were encountered: