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
When creating a test which sent lots of messages of different sizes between my client and a Go server, I discovered that the latency for small messages is relatively high. The latency for larger messages is very low.
Some detective work indicates that when the message size is 1448 bytes (including frame overhead, so a payload of 1440), then the latency is high. A message size of 1449 and larger leads to low latency.
Apparently, 1448 bytes is some type of max size for a TCP message. A friend indicated that one might attempt to set the TCP option TCP_NODELAY, which is an option to not buffer as much, or something.
This does not appear to be a bug in my client, per se, but given that WebSocket message may well be small in size, there should be an option to fix this, if possible.
The text was updated successfully, but these errors were encountered:
From the Distributed package in Base, the magic call to reduce latency for small messages is: ccall(:uv_tcp_nodelay, Cint, (Ptr{Void}, Cint), sock.handle, 1).
This needs to be an option during the connection, since I have no idea what the effects would be for all users.
When creating a test which sent lots of messages of different sizes between my client and a Go server, I discovered that the latency for small messages is relatively high. The latency for larger messages is very low.
Some detective work indicates that when the message size is 1448 bytes (including frame overhead, so a payload of 1440), then the latency is high. A message size of 1449 and larger leads to low latency.
Apparently, 1448 bytes is some type of max size for a TCP message. A friend indicated that one might attempt to set the TCP option TCP_NODELAY, which is an option to not buffer as much, or something.
This does not appear to be a bug in my client, per se, but given that WebSocket message may well be small in size, there should be an option to fix this, if possible.
The text was updated successfully, but these errors were encountered: