Closed
Bug 1421304
Opened 8 years ago
Closed 7 years ago
[meta] Mark various chrome initiated requests with expected large responses as Throttlable
Categories
(Firefox :: General, enhancement, P2)
Firefox
General
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox59 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
Details
(Keywords: meta, Whiteboard: [fxperf])
There is probably a number of requests expecting a large response, like update downloads, various sync updates etc, that could be marked as Throttleable so that the influence on active page load (bandwidth utilization) will be minimized.
Are these browser chrome requests in different components, or one? Should this bug be a meta to track changes to several places in the chrome or can we do this in one bug?
Flags: needinfo?(past)
Comment 2•8 years ago
|
||
I think we should treat this as a meta bug, yes. The code most certainly belongs in different bugzilla components and likely in different source modules, too.
Flags: needinfo?(past)
![]() |
Reporter | |
Comment 3•8 years ago
|
||
(In reply to Panos Astithas [:past] (please ni?) from comment #2)
> I think we should treat this as a meta bug, yes. The code most certainly
> belongs in different bugzilla components and likely in different source
> modules, too.
Yes.
Keywords: meta
Summary: Mark various chrome initiated requests with expected large responses as Throttlable → [meta] Mark various chrome initiated requests with expected large responses as Throttlable
![]() |
Reporter | |
Updated•8 years ago
|
Priority: -- → P2
Updated•7 years ago
|
Whiteboard: [fxperf]
Comment 4•7 years ago
|
||
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:Dolske, maybe it's time to close this bug?
Flags: needinfo?(dolske)
Comment 5•7 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte] from comment #4)
The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:Dolske, maybe it's time to close this bug?
Redirecting needinfo to Panos, as I think he's more appropriate to answer this.
Flags: needinfo?(dolske) → needinfo?(past)
![]() |
Reporter | |
Comment 6•7 years ago
|
||
Note that throttling has been disabled recently for causing various media playback issues. There is currently no plan to revamp it.
Comment 7•7 years ago
|
||
Justin is now the triage owner, but from comment 6 it sounds like we should just close this.
Flags: needinfo?(past) → needinfo?(dolske)
Comment 8•7 years ago
|
||
Refile if work resumes.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(dolske)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•