Improve performance after protocol changes #11

Closed
opened 2026-10-16 02:52:02 -04:00 by michael · 1 comment
Owner

The protocol changes caused a substantial performance regression, especially for the web client.

The protocol changes caused a substantial performance regression, especially for the web client.
Author
Owner

Performance has been improved, at the temporary cost of reduced length padding.

Unfortunately, the browser WebSocket APIs do not support streaming processing of message content. The final solution then is to reduce WebSocket message size (currently to 32 KiB) and then pad the sent messages with additional zero-length segments. Currently, only the first half of this is implemented, so padding is temporarily reduced to 32 KiB.

Resolving this regression will be tracked by #3.

Performance has been improved, at the temporary cost of reduced length padding. Unfortunately, the browser WebSocket APIs do not support streaming processing of message content. The final solution then is to reduce WebSocket message size (currently to 32 KiB) and then pad the sent messages with additional zero-length segments. Currently, only the first half of this is implemented, so padding is temporarily reduced to 32 KiB. Resolving this regression will be tracked by #3.
Sign in to join this conversation.
No labels
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
michael/secure-wormhole#11
No description provided.