1474912 - HTTP Response throttling v2 too aggressive: Switching to tabs with data (streams) being received pauses data on inactive tabs

Status: RESOLVED WONTFIX

(Core :: Networking: HTTP, defect, P5)

Description

[Honza Bambas (:mayhemer)]

+++ This bug was initially created as a clone of Bug #1462906 +++

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180516032328

Steps to reproduce:

An example could be having two Twitch or YouTube streams open at once in separate tabs.



Actual results:

Once switched to another tab, the inactive tab no longer receives data and will eventually cause the stream to buffer until it is the active tab again.

Basically the current active tab will "steal" the internet from inactive tabs while it is receiving data.

This bug appears to be present in the latest Beta and Nightly but not present in the latest stable release 60.0.1.

---

P3 because there is no immediate regression (change reverted) and v1 vs v2 throttling perf impact is not critical in any way.

Still I would like to fix/improve this in a short-mid time range.

Comment 1

[Honza Bambas (:mayhemer)]

To add few notes:

- we have no data on what are the best values for tweaking the throttling v2 parameters and whether they should somehow be even evolving dynamically ; the current set is based on manual testing with my home network

- I think throttling may use a similar mechanism as FastBlock is (now) using to disable itself when a page has reached a certain loading event, being it domcontentloaded, onload, interaction or just a timeout since page load start

- only study ran on http response throttling was a compare of v1 and v2 in bug 1434388

Comment 2

[Honza Bambas (:mayhemer)]

Throttling is disabled and the next step to improve the feature is to first establish experiments to figure out properly when and what to actually throttle, if at all.

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)

Comment 4

[Manuel Bucher [:manuel]]

Current intention seems to be to not investigate further in throttling v2 (see Bug 1462906 comment 42). If that changes (see Bug 1870091), then this would be needed to revised again.