15 ms·
Justin, this is awesome! The overhead of websocket is also surprising when all layers are considered including TCP Frames http://tavendo.com/blog/post/dissecti
by stephenblum 12y ago
Justin, this is awesome! The overhead of websocket is also surprising when all layers are considered including TCP Frames http://tavendo.com/blog/post/dissecting-websocket-overhead/ http://tavendo.com/blog/post/dissecting-websocket-overhead/
- jkarneges 12y agoInteresting! I'm surprised that browsers wouldn't batch up many outbound messages into single TCP frames. The server behaves more the way I would expect. That reminds me of a related point: The number of TCP frames can be considered more important than the number of bytes-per-frame when it comes to network performance. Most message exchanges, whether over WebSocket or HTTP, will occupy a comparable number of TCP frames, even if HTTP uses more bytes for the headers.