Requests causing delay in other request like they were executed in serial instead of parallel.
I'm noticing this especially watching stream on twitch and editing documents in google drive. Every thing I type is getting sent to google by XHR request to save document progress. As soon I start type streaming being delayed and finally starts to buffer.
I have checked if chrome hiccups too but it doesn't. I can use firefox to watch stream and other browser to browse and it won't hiccup neither.
I have tried to run firefox in safe mode with plugins off.
The stream quality doesnt matter, even 160p stream will start to buffer, and even if there is 15s buffer or even more - it will start to buffer again because of how delayed request become because of concuring ones. So that rules out network bottleneck for sure.
There is video that shows the issue: https://www.youtube.com/watch?v=ZydKcBPI6KU
Geändert am von KoKa
Ausgewählte Lösung
I think turning off throttle is fine if performance doesn't lag. If you notice problems, I guess you would want to close background tabs you don't need.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (3)
Does it seem that when a window or tab loses focus to another window or tab, the page that has gone into the background pauses? Try this workaround to reduce "throttling" of background media:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.
(2) In the search box above the list, type or paste throttle and pause while the list is filtered
(3) Double-click the network.http.throttle.version preference and modify the value from 2 to 1 and then click OK
Does that work on yours?
I have "app.normandy.startupExperimentPrefs.network.http.throttle.version" and "network.http.throttle.version" set both to 1 already, I changed "network.http.throttle.enable" from true to false and it made a difference, editing google docs doesn't cause stream to buffer anymore, but should I keep throttle disabled? Are there any cons to have it disabled? Can I have it set up per domain, so I would set it disabled for twitch and enabled for anything else?
Geändert am von KoKa
Ausgewählte Lösung
I think turning off throttle is fine if performance doesn't lag. If you notice problems, I guess you would want to close background tabs you don't need.