Very poor WebSocket send performance when streaming a file
Reported by
tapitma...@gmail.com,
Dec 10
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Steps to reproduce the problem: 1. Run any simple websocket server (can used attached node server.js file) 2. Run any simple HTTP server for hosting index.html 3. Open index.html in Chrome 4. Open a relatively large file What is the expected behavior? File streams at a reasonable bitrate. UI remains responsive. This is the behavior in Firefox. What went wrong? The file streams very slowly, and the UI locks up. Fan on my laptop goes crazy. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 71.0.3578.80 Channel: n/a OS Version: Arch 4.19.2 Flash Version:
,
Dec 11
One thing to be careful of is that WebSockets are horribly slow to send large messages with DevTools open. This is because it copies all the messages. There's no way to turn this feature off, you just have to make sure you do measurements with DevTools closed. On my machine, Chrome finishes sending a 1GB file in 5 seconds compared to 30 for Firefox.
,
Dec 11
,
Dec 11
Wow this makes a huge difference! Essentially solves my problem, assuming I never need to do lower level debugging. Any idea why Firefox doesn't have the same slowdown? I'm assuming they just aren't providing whatever features require copying the messages.
,
Dec 11
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
,
Dec 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by pbomm...@chromium.org
, Dec 10Components: Blink>Network>WebSockets
Labels: Needs-Triage-M71