send File(size 1.7MB)

Firefox, only one Websocket Binary Frame. Cost 329ms.

Chorme, 15 Websocket Binary Frame. About 112KB per frame. Cos 2214ms.

I found a bug report in 2015: https://bugs.chromium.org/p/chromium/issues/detail?id=517090

After test. The reason is server do not support "Receive fragmented message". When i change the server from netty to Gorilla WebSocket, the problem solved. Just one frame posted by chrome. But speed of chrome is slower than firefox too.

I`m dev file server in Intranet. The Bandwidth is 100MB/second. I want to split File myself with File.slice(), so i can control the performance myself and get the progress info.

The most critical problem is most websocket server do not support "Receive fragmented message".

> The most critical problem is most websocket server do not support "Receive fragmented message".

Fragmented message is a requirement of RFC6455. Are you saying that most websocket servers don't comply with it?

By the way, sending a blob is very inefficient in Chrome. Please see issue 571656.

For a 600KB message the extra overhead is 70 bytes, or 0.01%. Chrome's WebSockets are reportedly slower than Firefox's, but message fragmentation is not the cause.

Yes, most websocket servers don't fully support RFC6455.

I want to replace ajax with websocket. So, i must solve this problem. Chrome can not adjust anything now, i will try to change my server side.

I will complete the migration(from netty to Gorilla WebSocket) of the websocket server tomorrow.

Chrome is my lovest chioce. Please make the performace of websocket to the best.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Frame sizes are working as intended. Dupping against issue 865001 for the performance.